From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA/Linux] Ask kernel to kill inferior when GDB terminates
Date: Fri, 14 Nov 2014 17:09:00 -0000 [thread overview]
Message-ID: <54663729.6010708@redhat.com> (raw)
In-Reply-To: <1415984034-27122-1-git-send-email-brobecker@adacore.com>
On 11/14/2014 04:53 PM, Joel Brobecker wrote:
> Hello,
>
> This patch enhances GDB on GNU/Linux systems to ask the kernel
> to kill the inferior if GDB terminates without doing it itself.
> This would typically happen when GDB encounters a problem and
> crashes, or when it gets killed by an external process. This can
> be observed by starting a program under GDB, and then killing
> GDB with signal 9. After GDB is killed, the inferior still remains
> in "interruptible sleep (waiting for an event to complete)" state.
I could see this making some sense when GDB has spawned the process,
but it seems harsh when GDB has attached to the process instead
of spawning it?
Note that Windows has had a similar feature for
ages (DebugSetProcessKillOnExit), and how windows-nat.c calls
DebugSetProcessKillOnExit(false) when GDB attaches to a process.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-11-14 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 16:54 Joel Brobecker
2014-11-14 17:09 ` Pedro Alves [this message]
2014-11-14 17:33 ` Joel Brobecker
2014-11-19 9:25 ` Joel Brobecker
2014-11-19 9:58 ` Pedro Alves
2014-12-13 16:28 ` Joel Brobecker
2014-12-15 13:22 ` Pedro Alves
2014-12-15 20:43 ` Joel Brobecker
2014-12-15 21:17 ` Pedro Alves
2014-12-16 0:39 ` Joel Brobecker
2014-12-16 9:46 ` Pedro Alves
2014-12-16 12:58 ` pushed: " 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=54663729.6010708@redhat.com \
--to=palves@redhat.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).