While debuging a remote multithread program by means of gdb/gdbserver, frequently I see gdb complaints like this:
Program received signal SIG32, Real-time event 32.
0x400d7e84 in ?? ()
(gdb)
Then gdb is suspended to wait for new commands, and on this occasion, typing 'c' can make the debuging continue. But instruction 'info threads' can not list correct information.
In fact, this results from stripped libpthread/libthread_db, which can be easily verified by means of '/usr/bin/file'. To remove the problem, simply refer the libs to unstripped versions via gdb instructions like:
set solib-absolute-prefix [dir]
set solib-search-path [dir1];[dir2]
阅读(2069) | 评论(0) | 转发(0) |
