From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 199EC3858C2D; Mon, 25 Apr 2022 13:22:32 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 199EC3858C2D
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/18772] gdb does not respond to CTRL-C
Date: Mon, 25 Apr 2022 13:22:31 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: remote
X-Bugzilla-Version: 7.9
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: aburgess at redhat dot com
X-Bugzilla-Status: REOPENED
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: bug_status resolution
Message-ID: <bug-18772-4717-CCwp7qCvvF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18772-4717@http.sourceware.org/bugzilla/>
References: <bug-18772-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2022 13:22:32 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D18772

Andrew Burgess <aburgess at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---

--- Comment #11 from Andrew Burgess <aburgess at redhat dot com> ---
(In reply to Rich Surgenor from comment #10)

> Did you confirm that the pgid was !=3D to the pid in your testing? In my =
case,
> the pgid did not match the pgid or pid of any processes, resulting in the
> signal not getting sent anywhere.

OK, that's pretty interesting.  So I guess you started debugging some proce=
ss
that forks, you follow the fork, then you place the child into a different
process group?

Or am I overthinking this?

I'll try to craft a test that matches your description above later this wee=
k,
but any further hints you have about the nature of the failing situation wo=
uld
be great.=20=20

I'm reopening this issue for now.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=