User forums > Help

Irritating error message when debugging in XTerm

<< < (2/2)

oBFusCATed:
This won't work, because GDB must be a child process of C::B, because C::B needs to control it.
For this purpose we're starting gdb directly and also start a terminal using something like "xterm -e sleep randomnumber"
Then we use the tty command to tell gdb which terminal (tty) to use.

Jenna:
It has nothing to do with C::B and xterms -e parameter or anything like this.
You can get it without any IDE, just two terminals and gdb.
Open one terminal, get it's tty, start gdb from a second terminal, but use the first one as control terminal with the --tty parameter, run a prigram from inside gdb and you get the warning.

I've read that running netbeans with sudo fixes the warning, that doesn't work for C::V or gdb in console.

The (real?) cause seems to be in linux kernel or better in the way we (have to) start gdb:
http://stackoverflow.com/questions/7407088/kdevelop-debugging-warning-failed-to-set-controlling-terminal-operation-not-pe

Napoleon:
Well, thanks for having a look, and I'll just continue enjoying C::B's ease of use and wait and see what happens in the mean time.

Navigation

[0] Message Index

[*] Previous page