Code::Blocks Forums
User forums => Help => Topic started by: hagai_sela on November 01, 2009, 09:52:10 pm
-
Hi,
I just upgraded to ubuntu 9.10, and I am getting this error when I start the debugger:
"warning: GDB: failed to set controlling terminal: operation not permitted"
I am using the binary build (8.02).
Thanks,
Hagai.
-
"warning: GDB: failed to set controlling terminal: operation not permitted"
Mind using Google before?
http://www.google.com/search?q=warning%3A%20GDB%3A%20failed%20to%20set%20controlling%20terminal%3A%20operation%20not%20permitted
-
I did use google before, nothing seemed to be relevant.
-
I did use google before, nothing seemed to be relevant.
It is as it marks this as a gdb issue. So asking here is asking in the wrong forum. Sorry.
-
Interesting.
I have the same problem and did a lot of searching via google. A couple folks had this exact problem when using Netbeans.
To correct the problem it appears they changed a NetBeans setting. Specifically, they changed the "console type:" setting from "external terminal" to "output window" and the problem disappeared.
So now I'm wondering if there is an analogous setting in Code::Blocks? I'm pretty new to this application and haven't been able to find such a setting. I also wondered if this might be a command you pass to gdb somehow but haven't found any likely candidates.
V/R
Adam
-
You can change your app's type to GUI based and then the debugger plugin won't show a terminal.
Also the whole output of your program will go to the debugger's log panes.
-
And what's more: it seems you can safely ignore this warning, because debugging works as expected here (debian unstable/experimantal 64-bit) with this warning.
-
Cool.
Thanks for the help.
To change the application type to GUI I used Project->Properties...->Build Targets tab. I then selected "GUI application" in the Type: dropdown box.
I noticed I also had to go to Settings->Compiler and debugger... Then I selected the "Debugger settings" on the left panel and checked the "Display debugger's log" check box.
A "Debugger (debug)" tab appeared at the bottom of the workspace and my output appeared there.
It also looks like I can keep using a terminal and simply ignore the warning as suggested by jens. I have noticed, however, that my application doesn't exit debug mode quite the same as it does when I do a normal "Run." When I run the program (simple Hello World) as a console application through the "Run" command, I get the message, "Press ENTER to continue." After you hit enter the terminal window closes. When I run the application using "Debug / Continue", the console appears, my output flashes on the screen, and the console quickly closes without the previous prompt. Its probably worth mentioning that I have checked the "Pause when execution ends" check box under Projects->Properties->Build targets tab
I'm not sure if that is a bug or not. Does Code::Blocks open and close the console or does gdb? In any event the "problem" is easy enough to deal with by simply setting a breakpoint on the return call in main().
I'm using Code::Blocks 8.02 on Ubuntu 9.10 with gdb 7.0.
Thanks again for the help.
BTW... I'm just getting back into programming after a ~10 year hiatus. I've tried a couple of the other linux open source based IDEs including KDevelop, Anjuta and Eclipse. So far Code::Blocks has been the easiest to get up and running. Thanks for the cool app.
V/R
Adam
-
I know that this conversation is quite old, but I just recognized that I have exactly the same behaviour:
same error message and also windows closing after ending the application immediately when I have started that by debugging.
I'm using code:blocks 10.05 and GDB 7.1 on an Ubuntu 10.04 LTS.
Has anyone found out more about the background of this strange message than to simply ignoring it?
kind regards
Tjareson
-
Same for me.
any news?
-
Same for me.
any news?
Just ignore as others do. This not your problem.