From: Daniel Jacobowitz <dan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Wait for exit after "target remote |"
Date: Thu, 02 Sep 2010 18:41:00 -0000 [thread overview]
Message-ID: <20100902171221.GM28036@caradoc.them.org> (raw)
In-Reply-To: <20100901020722.GV2986@adacore.com>
On Tue, Aug 31, 2010 at 07:07:22PM -0700, Joel Brobecker wrote:
> > 2010-08-30 Daniel Jacobowitz <dan@codesourcery.com>
> >
> > * config.in, configure: Regenerated.
> > * configure.ac: Check for waitpid.
> > * ser-pipe.c (pipe_close): Wait for the program to exit.
>
> FWIW, I think that this is an improvement over the previous situation.
> Leaving processes behind can be disastrous, whereas I also think that
> the chances of a process not dying after a SIGTERM are slim (likely
> unintentional).
Thanks. In that case, I've put this in (HEAD only).
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2010-09-02 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 19:12 Daniel Jacobowitz
2010-09-01 2:07 ` Joel Brobecker
2010-09-02 18:41 ` Daniel Jacobowitz [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=20100902171221.GM28036@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=brobecker@adacore.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).