From: Michael Snyder <msnyder@specifix.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: linux native, switch forks, always have a thread
Date: Wed, 30 Apr 2008 21:26:00 -0000 [thread overview]
Message-ID: <1209584275.4615.384.camel@localhost.localdomain> (raw)
In-Reply-To: <200804301536.30066.pedro@codesourcery.com>
On Wed, 2008-04-30 at 15:36 +0100, Pedro Alves wrote:
> I'd missed this case when I made linux native always have a thread.
>
> It's not perfect in the sense that switching forks ("restart"/"fork",
> not follow-fork-mode) in multi-threaded apps doesn't handle
> multi-threading correctly yet, but that is an already existing
> problem. We shall be getting back to that in a few weeks
> for multi-process support.
I think you'll find that fork is more-or-less undefined
in the context of a multi-threaded program, meaning that
it's not terribly urgent that we try to handle this case.
next prev parent reply other threads:[~2008-04-30 19:38 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 [this message]
2008-05-01 20:36 ` Daniel Jacobowitz
2008-05-01 22:52 ` 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=1209584275.4615.384.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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