How to debug this issue without stack? I found out the problem is due to gdb happening with pthread program. gdb-6.3, gdb-6.4 may have problem to trace threaded program (no stack). You may see errors like these:
thread_db_get_info: cannot get thread info: generic error
Program Terminated with signal SIGABRT, Aborted. The program no longer exists.
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
Program received signal SIGTRAP, Trace/breakpoint trap.[Switching to Thread -1210313024 (LWP 16379)]0xb7ee0871 in __nptl_create_event () from /lib/tls/libpthread.so.0(gdb) where#0 0xb7ee0871 in __nptl_create_event () from /lib/tls/libpthread.so.0#1 0xb7ee1a20 in __nptl_deallocate_tsd () from /lib/tls/libpthread.so.0Previous frame inner to this frame (corrupt stack?)
which crashed in pthread_create()
If you see above errors and find no way to debug it, you may try to download and compile gdb-6.6. The problem was fixed in gdb-6.6.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment