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 329A43857C41; Sun, 24 Apr 2022 22:27:40 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 329A43857C41
From: "richsurgenor at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/18772] gdb does not respond to CTRL-C
Date: Sun, 24 Apr 2022 22:27:39 +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: richsurgenor at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
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: <bug-18772-4717-J7cSkpzQbP@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: Sun, 24 Apr 2022 22:27:40 -0000

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

--- Comment #10 from Rich Surgenor <richsurgenor at gmail dot com> ---
(In reply to Andrew Burgess from comment #7)
> I tried to reproduce this issue with GDB 8.2 and 11.2 on x86-64 GNU/Linux
> using Fedora 31, using the test program from the original comment.
>=20
> I can't see any problems interrupting GDB using Ctrl-C.  I tested this us=
ing
> 'continue', 'next', and 'step' commands, and in all cases GDB interrupts =
as
> expected (i.e. comes to a stop).
>=20
> If any of the original bug reporters are still seeing this issue with a
> recent version of GDB, then please do follow up and we can reopen this bu=
g,
> but for no I propose that we close this issue.

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

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