bug-gdb
[Top][All Lists]
Advanced

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

help, gdb debug a multi-thread linux daemon.


From: zhuofeng.pei
Subject: help, gdb debug a multi-thread linux daemon.
Date: Tue, 31 Jul 2001 17:08:07 -0400

I used gdb5.0 (come with mandrake 7.2) to debug a multi-thread linux daemon.
When I attach the daemon , it is have no source code information for debug.
(??)
Can not trace at all. This is the stack information. I try to load the
symbol myself but failed.
I can not found the daemon loading start address.

(gdb) attach 9462
Attaching to Pid 9462
0x40734d7e in ?? ()
(gdb) bt
#0 0x40734d7e in ?? ()
#1 0x401c3dcf in ?? ()
#2 0x4013db32 in ?? ()
#3 0x401c1019 in ?? ()
#4 0x8059b4b in ?? ()
#5 0x406b0cbe in ?? ()
~

When I used GDB to load the daemon and run it , it always pop up SIG32
signal, after I disable
This signal, set a breakpoint in my source code, GDB break with a SIGTRAP
signal, but can
not break at my breakpoint to trace the bug it stopped at libc code.
This the stack message.
received signal SIGTRAP, Trace/breakpoint trap.
0x40734d7e in select () from /lib/libc.so.6
(gdb) bt
#0 0x40734d7e in select () from /lib/libc.so.6
………………
#5 0x8059b4b in main (argc=3, argv=0xbffff734) at main.cpp:474
#6 0x406b0cbe in __libc_start_main () from /lib/libc.so.6
any experiences about that are appreciate.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]