Re: cvs HEAD : got a SIGTRAP



Le 15.08.2004 14:59:10, Pawel Salek a écrit :
On 08/15/2004 02:26:19 PM, Jean-Luc Coulon (f5ibh) wrote:
Hi,

I was running balsa HEAD cvs in gdb and I got a SIGTRAB.
Unfortunately, there was no backtrace ...

[Thread 1118722992 (zombie) exited]
[New Thread 1118722992 (LWP 11571)]
[Thread 1118722992 (unknown thread_db state 1) exited]

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 1118722992 (unknown thread_db state 1)]
0x0826677c in ?? ()
(gdb) bt
#0  0x0826677c in ?? ()

My guess is your gdb has no support for debugging threaded programs:

"On most systems, GDB has no special support for debugging programs
which create additional processes using the `fork' function.  When a
program forks, GDB will continue to debug the parent process and the
child process will run unimpeded. If you have set a breakpoint in any
code which the child then executes, the child will get a `SIGTRAP'
signal which (unless it catches the signal) will cause it to terminate."

using gdb command "handle SIGTRAP ignore" may help - I do not know.

Yes, it works that way ....
But it is quite a bit strange. I've done some gdb session sometime ago without such a problem. Maybe there was a package upgrade in the meantime.

Regards

Jean-Luc

Pawel

Attachment: pgpWFif1RNXQb.pgp
Description: PGP signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]