From: Ankur Sheth <asheth@ixiacom.com>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Cc: Dan Kegel <dkegel@ixiacom.com>
Subject: gdbserver and multithreaded programs
Date: Fri, 14 Jun 2002 19:08:00 -0000 [thread overview]
Message-ID: <9A9C83C019F35D47A570460E87D5D8AB0186F76C@racerx.ixiacom.com> (raw)
We tried out today's cvs on a simple remote multithreaded program on x86,
ppc405 and sh4.
Results :
x86 - worked fine.
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?
Regards,
ankur
next reply other threads:[~2002-06-15 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 19:08 Ankur Sheth [this message]
2002-06-14 19:17 ` Dan Kegel
2002-06-14 21:04 ` Daniel Jacobowitz
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=9A9C83C019F35D47A570460E87D5D8AB0186F76C@racerx.ixiacom.com \
--to=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