From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122355 invoked by alias); 15 Sep 2015 01:33:29 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 122324 invoked by uid 48); 15 Sep 2015 01:33:28 -0000 From: "jmgao at google dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18945] gdbserver cannot be interrupted on linux when pgid doesn't match pid Date: Tue, 15 Sep 2015 01:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.10 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jmgao at google dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q3/txt/msg00291.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=18945 --- Comment #4 from Josh Gao --- 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//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.