From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Warn about what will happen to all inferiors on "quit"
Date: Fri, 14 Nov 2008 11:14:00 -0000 [thread overview]
Message-ID: <491CB555.4070006@vmware.com> (raw)
In-Reply-To: <20081113230000.GP5112@adacore.com>
Joel Brobecker wrote:
>> I wonder if you might want to iterate thru the attached/child
>> processes, and give the user a choice about what to do with each
>> one?
>
> In my opinion, it would be too painful in practice for the default
> case. If the user decides to not follow the default, he can still
> cancel the "quit", and then use detach and kill for the processes
> he wants to treat differently. Once done, he can quit.
Sounds reasonable.
next prev parent reply other threads:[~2008-11-13 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 1:54 Pedro Alves
2008-11-14 7:03 ` Michael Snyder
2008-11-14 8:40 ` Joel Brobecker
2008-11-14 11:14 ` Michael Snyder [this message]
2008-11-14 8:37 ` Joel Brobecker
2008-11-15 16:11 ` [RFA] " Pedro Alves
2008-11-15 23:36 ` Joel Brobecker
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=491CB555.4070006@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.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