From: Dan Kegel <dank@kegel.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver and multiple threads update?
Date: Tue, 14 May 2002 09:02:00 -0000 [thread overview]
Message-ID: <3CE135D7.FBE843D7@kegel.com> (raw)
In-Reply-To: <20020514153206.GA32379@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> On Mon, May 13, 2002 at 11:51:57PM -0700, Dan Kegel wrote:
> > Daniel said he was very close to getting gdbserver
> > to handle multithreaded programs. I'd give my right
> > pinky for that... it'd make life much easier once in
> > a while, during release crunches when big multithreaded
> > programs somebody else wrote mysteriously fall over.
> >
> > So how's it going? Can we airdrop you a pizza or two?
>
> It's done. I hope to be finished with the last thing I need to do
> before submitting it by Friday.
Hot dog. As soon as it's posted here, I'll give it a spin
on ppc405, ppc750, and sh4.
Thanks,
Dan
prev parent reply other threads:[~2002-05-14 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 23:48 Dan Kegel
2002-05-14 8:32 ` Daniel Jacobowitz
2002-05-14 9:02 ` Dan Kegel [this message]
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=3CE135D7.FBE843D7@kegel.com \
--to=dank@kegel.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