From: Dan Kegel <dkegel@ixiacom.com>
To: 'Daniel Jacobowitz ' <drow@mvista.com>, Ankur Sheth <asheth@ixiacom.com>
Cc: "''gdb@sources.redhat.com' '" <gdb@sources.redhat.com>,
Dan Kegel <dkegel@ixiacom.com>
Subject: RE: gdbserver and multithreaded programs
Date: Fri, 14 Jun 2002 23:17:00 -0000 [thread overview]
Message-ID: <9A9C83C019F35D47A570460E87D5D8AB027592DF@racerx.ixiacom.com> (raw)
Daniel Jacobowitz wrote:
> > ppc405 - worked on single threaded program, but on multithreaded
> > program output zillions of
> >
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > as soon as we tried to step thru main.
> >
> > sh4 - worked fine on single threaded program, but on
> > multithreaded program it output the following message.
> >
> > Program received signal SIG32, Real-time event 32.
>
> The "received signal SIG32" means that thread_db did not load. Most
> likely this means GDB did not find your libraries. On ppc405 I'd guess
> that it found an incorrect copy of the libraries. Are you setting
> solib-absolute-prefix correctly?
No, we weren't setting it at all. Thanks for the tip; works much
better now on ppc405. I did see a strange message
"Program received signal SIGTRAP, Trace/breakpoint trap."
a few times, but in general I'm able to step through a program
that creates lots of threads on ppc405 now. Huzzah!
(Haven't tried sh4 again yet.)
Still not trivial to build and use in a cross-compiled environment
(what is?), but a good FAQ ought to help that.
Thanks for the fast help!
- Dan
next reply other threads:[~2002-06-15 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 23:17 Dan Kegel [this message]
2002-06-16 20:44 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-06-14 19:08 Ankur Sheth
2002-06-14 19:17 ` Dan Kegel
2002-06-14 21:04 ` Daniel Jacobowitz
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=9A9C83C019F35D47A570460E87D5D8AB027592DF@racerx.ixiacom.com \
--to=dkegel@ixiacom.com \
--cc=asheth@ixiacom.com \
--cc=drow@mvista.com \
--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