This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
gdbserver multithread support broken in 5.2.1?
- From: Dan Kegel <dkegel at ixiacom dot com>
- To: gdb at sources dot redhat dot com
- Date: Fri, 26 Jul 2002 17:53:59 -0700
- Subject: gdbserver multithread support broken in 5.2.1?
With gdb+dejagnu-weekly-CVS-20020709, remote debugging works fine on ppc405.
With gdb-5.2.1 built the same way, it doesn't seem to work, and I
get the error message
GDB bug: target.c (target_signal_from_host): unrecognized real-time signal
from gdbserver.
The problem seems to be in gdbserver, as the new gdb works fine with the old
gdbserver. When I debug a trivial 9-threaded program:
the breakpoint on main works fine, but a breakpoint on the first created
thread's main routine fails. Here's the gdb log:
(gdb) target remote 10.0.1.1:1234
Remote debugging using 10.0.1.1:1234
0x30013ae8 in ?? ()
(gdb) break main
Breakpoint 1 at 0x10000a00: file atomicity_test.c, line 46.
(gdb) cont
Continuing.
Breakpoint 1, main (argc=1, argv=0x7ffffe84) at atomicity_test.c:46
46 int switches = 0;
(gdb) break my_thread_main
Breakpoint 2 at 0x10000964: file atomicity_test.c, line 33.
(gdb) cont
Continuing.
And here's the log on the remote system:
# gdbserver foo:1234 ./a.out
Process ./a.out created; pid = 452
Remote debugging from host 192.168.6.130
nthreads 8, nloops 100000, nrepeats 100
GDB bug: target.c (target_signal_from_host): unrecognized real-time signal
There wasn't much time between those two releases, so it shouldn't be
too hard to track the problem down. I haven't looked at the
diffs yet; I was kind of hoping somebody would know what was up...
(In both cases, I had applied a patch to give an initial value for
solib-absolute-prefix, but it's hard to imagine that was causing a problem...)
Thanks for any suggestions!
- Dan