gdb thread support doesn't work
i filed bug #28058, is someone gonna fix it? this is quite critical.
Program received signal SIGUSR1, User defined signal 1.
0x4008fa54 in ()
(gdb) s
Single stepping until exit from function __syscall_sigsuspend,
which has no line number information.
0x4003aa8b in sigsuspend ()
(gdb) s
Single stepping until exit from function sigsuspend,
which has no line number information.
0x4001610d in pthread_create ()
(gdb) s
Single stepping until exit from function pthread_create,
which has no line number information.
tpool_init (tpoolp=0xbffffb68, num_worker_threads=10, max_queue_size=20,
do_not_block_when_full=0) at tpool.c:60
60 for (i = 0; i != num_worker_threads; i++) {
(gdb) info threads
(gdb) thread 1
Thread ID 1 not known. Use the "info threads" command to
see the IDs of currently known threads.
(gdb)
extract from info gdb:
*Warning:* These facilities are not yet available on every GDB
configuration where the operating system supports threads. If
your GDB does not support threads, these commands have no effect.
For example, a system without thread support shows no output from
`info threads', and always rejects the `thread' command, like this:
(gdb) info threads
(gdb) thread 1
Thread ID 1 not known. Use the "info threads" command to
see the IDs of currently known threads.
Reply to: