From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 6/6] Add test that exercises the inferior being killed while stopped under GDB
Date: Tue, 14 Jul 2015 10:22:00 -0000 [thread overview]
Message-ID: <55A4E2D6.20701@redhat.com> (raw)
In-Reply-To: <1425671886-7798-7-git-send-email-palves@redhat.com>
On 03/06/2015 07:58 PM, Pedro Alves wrote:
> This exercises the case of the inferior disappearing while GDB is
> debugging it, such as something doing "kill -9 PID" while the program
> is stopped under GDB or GDBserver. This triggered a set of internal
> errors, fixed by the previous patches.
>
> gdb/testsuite/ChangeLog:
> 2015-03-06 Pedro Alves <palves@redhat.com>
>
> * gdb.base/killed-outside.exp: New file.
> * gdb.base/killed-outside.c: New file.
I pushed this in.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-07-14 10:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 19:58 [PATCH 0/6] Fix problems if inferior disappears while being debugged Pedro Alves
2015-03-06 19:58 ` [PATCH 4/6] native/Linux: internal error if inferior disappears after stopped by breakpoint Pedro Alves
2015-03-19 12:37 ` [pushed] native/Linux: internal error if resume is short-circuited (Re: [PATCH 4/6] native/Linux: internal error if inferior disappears after stopped by breakpoint) Pedro Alves
2015-03-19 12:49 ` [pushed] gdbserver/Linux: unbreak thread event randomization (Re: [pushed] native/Linux: internal error if resume is short-circuited) Pedro Alves
2015-03-19 16:14 ` [PATCH] gdbserver/Linux: Unbreak non-stop (Re: [pushed] gdbserver/Linux: unbreak thread event randomization) Pedro Alves
2015-03-19 16:54 ` [pushed] " Pedro Alves
2015-03-06 19:58 ` [PATCH 5/6] gdbserver/Linux: internal error when killing a process that is already gone Pedro Alves
2015-03-06 19:58 ` [PATCH 3/6] Fix race exposed by gdb.threads/killed.exp Pedro Alves
2015-03-19 17:39 ` Pedro Alves
2015-03-06 19:58 ` [PATCH 2/6] Introduce throw_ptrace_error Pedro Alves
2015-03-06 21:04 ` Mark Kettenis
2015-03-06 21:40 ` Pedro Alves
2015-03-08 20:30 ` Mark Kettenis
2015-03-08 21:48 ` Pedro Alves
2015-03-10 14:53 ` Mark Kettenis
2015-03-11 15:44 ` Pedro Alves
2015-03-19 17:33 ` [pushed] Fix race exposed by gdb.threads/killed.exp (Re: [PATCH 2/6] Introduce throw_ptrace_error) Pedro Alves
2015-03-06 19:58 ` [PATCH 1/6] Move throw_perror_with_name to common/ Pedro Alves
2015-03-06 20:27 ` [PATCH 6/6] Add test that exercises the inferior being killed while stopped under GDB Pedro Alves
2015-07-14 10:22 ` Pedro Alves [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=55A4E2D6.20701@redhat.com \
--to=palves@redhat.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