From: Jim Blandy <jimb@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Nathan Sidwell <nathan@codesourcery.com>, gdb@sourceware.org
Subject: Re: Non-stop multi-threaded debugging
Date: Tue, 20 Nov 2007 20:12:00 -0000 [thread overview]
Message-ID: <m3oddoznf9.fsf@codesourcery.com> (raw)
In-Reply-To: <18243.13661.579428.128690@kahikatea.snap.net.nz> (Nick Roberts's message of "Wed, 21 Nov 2007 08:28:29 +1300")
Nick Roberts <nickrob at snap.net.nz> writes:
> > - We're to implement asynchronous interaction with GDB.
> >
> > GDB will be responsive to commands while the program is running.
> > This is mostly a consequence of supporting non-stop multi-threaded
> > debugging: it's the degenerate case where no threads happen to be
> > stopped.
>
> I don't expect Jim will cut his holiday short to answer this, so this is
> for when he gets back:
>
> Will this use any of the code in the patch that I sent you, or will you use
> an entirely different approach?
We won't be using an entirely different approach; the existing event
loop seems to be adequate for most purposes. And we'll certainly need
to do something like what you did with the async_signal_hook. So it's
likely we'll be using at least portions of your patch.
next prev parent reply other threads:[~2007-11-20 20:12 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 [this message]
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
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=m3oddoznf9.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=nathan@codesourcery.com \
--cc=nickrob@snap.net.nz \
/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