From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 123106 invoked by alias); 5 Aug 2015 11:32:41 -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 123055 invoked by uid 48); 5 Aug 2015 11:32:40 -0000 From: "moorel at ntlworld dot com" To: gdb-prs@sourceware.org Subject: [Bug remote/18772] New: gdb does not respond to CTRL-C Date: Wed, 05 Aug 2015 11:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: moorel at ntlworld 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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/msg00150.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=18772 Bug ID: 18772 Summary: gdb does not respond to CTRL-C Product: gdb Version: 7.9 Status: NEW Severity: critical Priority: P2 Component: remote Assignee: unassigned at sourceware dot org Reporter: moorel at ntlworld dot com Target Milestone: --- Hi Support, it looks like a bug has been introduced, somewhere between 7.5 & 7.9. I do not have all the intermediate builds available to narrow this down. I have a very simple testcase, running on Fedora Linux, but appears to be a general issue I even reproduced on an ARM target. 1: #include 2: int main() { 3: int cond = 0; 4: while(cond == 0) { /* do nothing */ } // BREAK at this line 5: return 0; 6: } compile for debug $ gcc -g -o app.exe app.c run the application in gdbserver $ gdbserver localhost:9999 app.exe in gdb do the following $ gdb app.exe (gdb) target remote localhost:9999 (gdb) b app.c:4 (gdb) continue (gdb) next so now gdb is trying to run to the 'next' line, which it cannot reach because the condition in the while loop is always true, so interrupt by sending CTRL-C (gdb) ^C nothing happens The session is now locked up, if you issue another CTRL-C, the gdb client will Quit (gdb)^CQuit The gdbserver is still running, but I have failed to interrupt Try the same with gdb version 7.5 and it works Thx Lee -- You are receiving this mail because: You are on the CC list for the bug.