From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Some more multi-fork fixes
Date: Fri, 27 Jan 2006 20:04:00 -0000 [thread overview]
Message-ID: <43DA7BFE.2070100@redhat.com> (raw)
In-Reply-To: <20060115190757.GA10454@nevyn.them.org>
Daniel Jacobowitz wrote:
> These patches allow multi-fork.exp to pass on x86_64-pc-linux-gnu, most of
> the time. I'm sorry I didn't notice the _dl_sysinfo_int80 bit earlier.
Thanks, I'd been thinking about that...
> Some other problems I noticed, but did not fix:
>
> The "follow child, print pids" test is victim of a race condition; sometimes
> the "$pid done" printout from the inferior will be interleaved with the GDB
> output, causing expect to mark the test as a failure.
>
> delete-fork really ought to call waitpid after deleting the fork; otherwise
> the process lives on as a zombie.
That's fine with me too.
next prev parent reply other threads:[~2006-01-27 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 19:08 Daniel Jacobowitz
2006-01-27 20:04 ` Michael Snyder [this message]
2006-02-24 23:10 ` Daniel Jacobowitz
2006-02-25 0:12 ` Daniel Jacobowitz
2006-03-10 19:50 ` Michael Snyder
2006-03-10 19:54 ` Daniel Jacobowitz
2006-03-10 20:04 ` Michael Snyder
2006-03-01 22:15 ` Michael Snyder
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=43DA7BFE.2070100@redhat.com \
--to=msnyder@redhat.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