gdbserver-6.6 threading support

Jon Ringle
2007-03-06T16:59:25Z

Hello all,

I found that during my testing of gdbserver and signals that I was not
actually varying the gdbserver used on the target. I was always using
gdbserver-6.5 and never gdbserver-6.6. When I actually did use
gdbserver-6.6 or gdbserver-6.6.50.20070306-cvs, I get the following from
my crossgdb:

ringlej@crossdev:~/src/gdbsignals-test$
~/build/armeb-linux-gdb-6.6/gdb/gdb ./gdbsignal-test
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu
--target=armeb-linux"...
(gdb) handle SIGUSR2 nostop noprint
Signal Stop Print Pass to program Description
SIGUSR2 No No Yes User defined signal 2
(gdb) b 106
Breakpoint 1 at 0x8b1c: file gdbsignal-test.c, line 106.
(gdb) target remote 192.168.205.10:5555
Remote debugging using 192.168.205.10:5555
warning: Remote failure reply: E01
0x400009f0 in _start () from
/scratchbox/compilers/armeb-linux-uclibc/lib/ld-uClibc.so.0
(gdb) cont
Continuing.

Program received signal SIG32, Real-time event 32.
0x400849a4 in __rt_sigsuspend () from
/scratchbox/compilers/armeb-linux-uclibc/lib/libc.so.0
(gdb) show solib-absolute-prefix
Prefix for loading absolute shared library symbol files is
"/scratchbox/compilers/armeb-linux-uclibc".

From other mailing list threads that I had read this seem to imply that
there was some mismatch between my target's libpthread.so and
libthread_db.so and the one in my host's solib-absolute-prefix. I found
that the two sets matched. Further, if I rebuild gdbserver-6.5 and use
the rebuilt gdbserver-6.5, it once again works.

Jon