From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] 07/10 non-stop inferior control
Date: Fri, 09 May 2008 02:52:00 -0000 [thread overview]
Message-ID: <20080509014454.GA22833@caradoc.them.org> (raw)
In-Reply-To: <200805090222.51406.pedro@codesourcery.com>
On Fri, May 09, 2008 at 02:22:51AM +0100, Pedro Alves wrote:
> Isn't this new_thread_event handling a bandaid for some
> misbehaving target? My understanding was that targets should handle
> new thread events (and call add_thread*) themselves nowadays.
That might be a little strong; but the Linux and remote targets do so,
because it was much more convenient.
> Since this is a new mode that will require adaptation
> by each target, it sounded reasonable to require that the
> the new_thread_event should never be hit, and that the
> target handles adding threads to GDB's thread list.
If documented in gdbint, I think this would be a reasonable new
restriction.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-09 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 17:43 Pedro Alves
2008-05-08 18:19 ` Eli Zaretskii
2008-05-09 2:08 ` Pedro Alves
2008-05-09 2:52 ` Daniel Jacobowitz [this message]
2008-05-19 16:55 ` Pedro Alves
2008-05-19 16:56 ` Pedro Alves
2008-06-04 11:49 ` Vladimir Prus
2008-06-04 12:07 ` Pedro Alves
2008-06-04 12:18 ` Vladimir Prus
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=20080509014454.GA22833@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@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