From: Daniel Jacobowitz <drow@false.org>
To: Markus.Grunwald@pruftechnik.com
Cc: Michael Snyder <gdb@sourceware.org>
Subject: Re: gdb continues when I want "next"
Date: Thu, 08 Mar 2007 15:01:00 -0000 [thread overview]
Message-ID: <20070308150114.GA4028@caradoc.them.org> (raw)
In-Reply-To: <OF9290451D.B995458B-ONC1257298.004E8C2D-C1257298.00518C25@pruftechnik.com>
On Thu, Mar 08, 2007 at 03:50:22PM +0100, Markus.Grunwald@pruftechnik.com wrote:
> > Can't really do that, you know... or at least, it's
> > likely to be quite unpredictable unles the *only* thing
> > the fork-child does is call exec.
>
> Could you explain this a bit further ?
There was conventionally trouble, but POSIX gives it a pretty clear
meaning, and I believe both LinuxThreads and NPTL get it right
nowadays.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-08 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 13:44 Markus.Grunwald
2007-03-02 13:57 ` Daniel Jacobowitz
2007-03-07 19:09 ` Michael Snyder
2007-03-08 14:50 ` Markus.Grunwald
2007-03-08 15:01 ` Daniel Jacobowitz [this message]
2007-03-07 11:20 Markus.Grunwald
2007-03-07 12:13 ` Daniel Jacobowitz
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=20070308150114.GA4028@caradoc.them.org \
--to=drow@false.org \
--cc=Markus.Grunwald@pruftechnik.com \
--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