This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/18945] gdbserver cannot be interrupted on linux when pgid doesn't match pid
- From: "jmgao at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 15 Sep 2015 01:33:27 +0000
- Subject: [Bug gdb/18945] gdbserver cannot be interrupted on linux when pgid doesn't match pid
- Auto-submitted: auto-generated
- References: <bug-18945-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18945
--- Comment #4 from Josh Gao <jmgao at google dot com> ---
Sending the signal to the process group feels somewhat wrong to me, since it
seems pretty likely that if PGID != PID, there're going to be other processes
in that group which we're not attached to.
Do you think iteratively pgkill'ing all of the threads in /proc/<pid>/task/*
would work? There's a race condition there if all of the threads in the process
disappear in between reading the directory entries and actually killing them,
but that seems a bit esoteric.
--
You are receiving this mail because:
You are on the CC list for the bug.