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 4AADC3857419; Sat, 16 Apr 2022 14:02:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4AADC3857419
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: Sat, 16 Apr 2022 14:02:12 +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: 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: bug_status cc resolution
Message-ID: <bug-18772-4717-S53sEJ7Ejs@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: Sat, 16 Apr 2022 14:02:13 -0000

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

Andrew Burgess <aburgess at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |aburgess at redhat dot com
         Resolution|---                         |WORKSFORME

--- Comment #7 from Andrew Burgess <aburgess at redhat dot com> ---
I tried to reproduce this issue with GDB 8.2 and 11.2 on x86-64 GNU/Linux u=
sing
Fedora 31, using the test program from the original comment.

I can't see any problems interrupting GDB using Ctrl-C.  I tested this using
'continue', 'next', and 'step' commands, and in all cases GDB interrupts as
expected (i.e. comes to a stop).

If any of the original bug reporters are still seeing this issue with a rec=
ent
version of GDB, then please do follow up and we can reopen this bug, but fo=
r no
I propose that we close this issue.

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