From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] linux_nat_kill() compat. with linux-2.4.x
Date: Sun, 16 Mar 2014 13:59:00 -0000 [thread overview]
Message-ID: <20140316135916.GA31463@host2.jankratochvil.net> (raw)
Hi,
it had been already approved by Tom that time so I will check it in in some time.
[patch] Fix SIGTERM signal safety (PR gdb/15358)
https://sourceware.org/ml/gdb-patches/2013-07/msg00094.html
Message-ID: <20130702200010.GA23478@host2.jankratochvil.net>
Doug has just asked to split it out of:
Re: [patchv2] Fix SIGTERM signal safety (PR gdb/15358) [refresh]
https://sourceware.org/ml/gdb-patches/2014-03/msg00342.html
Message-ID: <21284.44419.745786.47756@ruffy.mtv.corp.google.com>
The testcase of the patch above still PASSes for me on Fedora 20 x86_64 even
without this patch, I guess this patch was needed only on that 2.4.x Linux
kernel it mentions. I am no longer interested in 2.4.x so if anyone has any
concerns I am also fine with dropping this patch.
Thanks,
Jan
gdb/
2014-03-16 Jan Kratochvil <jan.kratochvil@redhat.com>
PR gdb/15358
* linux-nat.c (linux_nat_kill): Use kill_callback first.
Extend the comment for stop_callback.
diff --git a/gdb/linux-nat.c b/gdb/linux-nat.c
index b615423..ec84188 100644
--- a/gdb/linux-nat.c
+++ b/gdb/linux-nat.c
@@ -3777,8 +3777,15 @@ linux_nat_kill (struct target_ops *ops)
{
ptid_t ptid = pid_to_ptid (ptid_get_pid (inferior_ptid));
+ /* Kill all LWP's before trying to stop them. In rare cases the
+ lwp_info state may not match the inferior and
+ stop_wait_callback could lock up. */
+ iterate_over_lwps (ptid, kill_callback, NULL);
+
/* Stop all threads before killing them, since ptrace requires
- that the thread is stopped to sucessfully PTRACE_KILL. */
+ that the thread is stopped to sucessfully PTRACE_KILL.
+ kill_callback normally already turned the inferior into a zombie
+ except for old Linux kernels 2.4.x. */
iterate_over_lwps (ptid, stop_callback, NULL);
/* ... and wait until all of them have reported back that
they're no longer running. */
next reply other threads:[~2014-03-16 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 13:59 Jan Kratochvil [this message]
2014-05-21 12:49 ` Pedro Alves
2014-06-06 20:15 ` Jan Kratochvil
2014-06-09 10:29 ` Pedro Alves
2014-06-09 10:32 ` Jan Kratochvil
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=20140316135916.GA31463@host2.jankratochvil.net \
--to=jan.kratochvil@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