Hi:
I am trying to use gdbserver to remotely debug a multithreaded application.
Remote host is a IA32, running MontaVista Linux 3.0 kernel v 2.4.18; gdbserver
from the 5.3 release tarball, patched with the PREPARE_TO_PROCEED patch, and
built on the remote host.
Local host is an IA32 machine, running RedHat 8.0, gdb v 5.2.1-4.
I get a "Real-time event 32"-signal as each thread is spun up, execution
stops, and I have to re-continue. After all the threads are created and I hit
a breakpoint, info thread only displays the main thread.
I don't see this problem while debugging with gdb (5.2.1) on the remote (and
the local) target
.
Is there anything I can do to solve the problem I am experiencing with
gdbserver?
Here's gdb's output when debugging remotely:
--------------------------------------------
(gdb) target remote 192.168.139.14:8888
Remote debugging using 192.168.139.14:8888
0x40001390 in ?? ()
(gdb) b osevent.cxx:215
Breakpoint 1 at 0x826dd03: file ../../common/osevent.cxx, line 215.
(gdb) cont
Continuing.
Program received signal SIG32, Real-time event 32.
0x404b724d in ?? ()
(gdb) c
Continuing.
Program received signal SIG32, Real-time event 32.
0x404b724d in ?? ()
(gdb)
Continuing.
Program received signal SIG32, Real-time event 32.
0x404b724d in ?? ()
(gdb)
Continuing.
Program received signal SIG32, Real-time event 32.
0x404b724d in ?? ()
(gdb)
Continuing.
Program received signal SIG32, Real-time event 32.
0x404b724d in ?? ()
(gdb)
Continuing.
Program received signal SIG32, Real-time event 32.
0x404b724d in ?? ()
(gdb)
Continuing.
Program received signal SIG32, Real-time event 32.
0x404b724d in ?? ()
(gdb)
Continuing.
Breakpoint 1, OsEventManagerClass::eventLoop() (this=0x89caf78) at
../../common/osevent.cxx:215
215 if (pTimer) {
(gdb) info thread
1 Thread 3860 OsEventManagerClass::eventLoop() (this=0x89caf78) at
../../common/osevent.cxx:215
----------------------------------------------
Thanks,
--Nik