From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: linux native, switch forks, always have a thread
Date: Thu, 01 May 2008 22:52:00 -0000 [thread overview]
Message-ID: <200805012351.40266.pedro@codesourcery.com> (raw)
In-Reply-To: <20080501203540.GU22218@caradoc.them.org>
A Thursday 01 May 2008 21:35:40, Daniel Jacobowitz wrote:
> On Wed, Apr 30, 2008 at 03:36:30PM +0100, Pedro Alves wrote:
> > 2008-04-30 Pedro Alves <pedro@codesourcery.com>
> >
> > * linux-nat.c (linux_nat_switch_fork): Reinit GDB's thread list
> > and register the fork's PTID as a thread.
>
> OK. I wonder what this does to those thread creation notifications
> though... someone gets to sort that out during multi-process. :-)
It's in. Thanks. Yeah, the frontend gets no clue the process
changed, so this is undefined-land (yet) :-)
--
Pedro Alves
prev parent reply other threads:[~2008-05-01 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 16:42 Pedro Alves
2008-04-30 21:26 ` Michael Snyder
2008-05-01 20:36 ` Daniel Jacobowitz
2008-05-01 22:52 ` Pedro Alves [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=200805012351.40266.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=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