From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: About handle_inferior_event new_thread_event
Date: Mon, 29 Jun 2009 18:45:00 -0000 [thread overview]
Message-ID: <200906291946.26217.pedro@codesourcery.com> (raw)
In-Reply-To: <20090629175628.GA2823@caradoc.them.org>
On Monday 29 June 2009 18:56:28, Daniel Jacobowitz wrote:
> I don't know - but I do know that this code has never worked reliably
> for Linux; we used to get crashes or internal errors from unset
> LWP-private state any time we went through here. I'd rather all
> targets were required to do thread accounting on their own.
Yeah, although I don't think those should be happening currently.
linux-nat.c just ignores events from lwps not in the lwp_list... In non-stop
mode, it's already an internal error to reach this bit. I do
notice that nto-procfs.c is one target that defers adding threads to the
list to handle_inferior_event ... but I honestly doubt the new thread
needs a first-chance resume.
--
Pedro Alves
next prev parent reply other threads:[~2009-06-29 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 11:28 Pedro Alves
2009-06-29 17:56 ` Daniel Jacobowitz
2009-06-29 18:45 ` Pedro Alves [this message]
2009-06-29 18:06 ` Michael Snyder
2009-06-29 18:13 ` Pedro Alves
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=200906291946.26217.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--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