From: nak26 <nak26@drexel.edu>
To: gdb@sources.redhat.com
Subject: gdbserver multithreaded debugging problem
Date: Mon, 23 Jun 2003 19:39:00 -0000 [thread overview]
Message-ID: <3EF77554@webmail.drexel.edu> (raw)
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
next reply other threads:[~2003-06-23 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 19:39 nak26 [this message]
2003-06-23 19:45 ` Cal Erickson
2003-06-23 19:49 ` Daniel Jacobowitz
2003-06-24 14:54 nak26
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EF77554@webmail.drexel.edu \
--to=nak26@drexel.edu \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).