From: Nigel Stephens <nigel@mips.com>
To: gdb@sourceware.org
Subject: Re: Non-stop multi-threaded debugging
Date: Wed, 05 Dec 2007 20:01:00 -0000 [thread overview]
Message-ID: <14179465.post@talk.nabble.com> (raw)
In-Reply-To: <4743178A.3050501@codesourcery.com>
Nathan Sidwell wrote:
>
> Hi all,
>
> Jim Blandy prepared this, but is on vacation this week. So, I'm
> announcing it
> in his absence. Pretend I wrote 'sudo jimb ...'
>
> A client of CodeSourcery's has contracted with us to implement a
> number of new features in GDB, some of which have been on the
> frequently requested list for quite some time:
>
Cool. We'll be very interested in this work, particularly as it applies to
our CPUs with h/w multi-threading.
Nigel
--
View this message in context: http://www.nabble.com/Non-stop-multi-threaded-debugging-tf4844837.html#a14179465
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-12-05 20:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 17:21 Nathan Sidwell
2007-11-20 19:28 ` Nick Roberts
2007-11-20 20:12 ` Jim Blandy
2007-11-21 13:53 ` Michael Snyder
2007-11-26 23:13 ` Jim Blandy
2007-11-27 16:42 ` Ulrich Weigand
2007-11-30 20:48 ` Thiago Jung Bauermann
2007-12-04 18:17 ` Jim Blandy
2007-12-05 13:41 ` Fabian Cenedese
2007-12-05 20:01 ` Nigel Stephens [this message]
2007-11-28 5:18 Pawel Piech
2007-11-29 2:08 ` Nick Roberts
2007-11-29 6:15 ` Pawel Piech
2007-11-29 8:36 ` Vladimir Prus
2007-11-29 16:42 ` Pawel Piech
[not found] ` <474EEB36.1040203@windriver.com>
2007-11-29 16:46 ` Vladimir Prus
2007-11-29 17:36 ` Pawel Piech
2007-11-29 17:51 ` Vladimir Prus
2007-11-29 18:13 ` Pawel Piech
2007-12-04 18:34 ` Jim Blandy
2007-12-04 23:05 ` Pawel Piech
2007-12-05 21:52 ` Jim Blandy
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=14179465.post@talk.nabble.com \
--to=nigel@mips.com \
--cc=gdb@sourceware.org \
/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