From: Daniel Jacobowitz <drow@mvista.com>
To: 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 21:04:00 -0000 [thread overview]
Message-ID: <20020615040436.GA6116@nevyn.them.org> (raw)
In-Reply-To: <9A9C83C019F35D47A570460E87D5D8AB0186F76C@racerx.ixiacom.com>
On Fri, Jun 14, 2002 at 07:06:35PM -0700, Ankur Sheth wrote:
> We tried out today's cvs on a simple remote multithreaded program on x86,
> ppc405 and sh4.
Let's see what we can do for you.
> Results :
> x86 - worked fine.
OK...
> 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.
>
>
> Has anybody else tried this stuff yet?
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?
I'm trying to come up with better ways to diagnose this sort of
problem, as the remote multithread debug is exceedingly fragile at
present.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-06-15 4:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 19:08 Ankur Sheth
2002-06-14 19:17 ` Dan Kegel
2002-06-14 21:04 ` Daniel Jacobowitz [this message]
2002-06-14 23:17 Dan Kegel
2002-06-16 20:44 ` 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=20020615040436.GA6116@nevyn.them.org \
--to=drow@mvista.com \
--cc=asheth@ixiacom.com \
--cc=dkegel@ixiacom.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