public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "moorel at ntlworld dot com" <sourceware-bugzilla@sourceware.org> 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 [thread overview] Message-ID: <bug-18772-4717@http.sourceware.org/bugzilla/> (raw) 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 <stdio.h> 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.
next reply other threads:[~2015-08-05 11:32 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-05 11:32 moorel at ntlworld dot com [this message] 2020-04-20 8:55 ` [Bug remote/18772] " massimo.b at gmx dot net 2020-08-18 2:45 ` paul at sourceware dot m.darkrain42.org 2020-10-10 15:49 ` rarul at rarul dot com 2020-10-12 6:15 ` matic.kres at isystem dot si 2022-04-16 14:02 ` aburgess at redhat dot com 2022-04-19 10:26 ` moorel at ntlworld dot com 2022-04-24 22:08 ` richsurgenor at gmail dot com 2022-04-24 22:27 ` richsurgenor at gmail dot com 2022-04-25 13:22 ` aburgess at redhat dot com 2022-04-26 14:59 ` aburgess at redhat dot com 2022-06-22 10:52 ` ghjghj530-bubu at yahoo dot de 2022-06-22 16:42 ` pedro at palves dot net 2022-08-14 21:25 ` dominik.b.czarnota+bugzilla at gmail dot com 2022-08-30 8:40 ` filip.bascarevic at siemens dot com 2022-11-27 9:31 ` cvs-commit at gcc dot gnu.org 2023-03-20 15:53 ` eldar.abusalimov at jetbrains dot com 2023-03-21 14:58 ` tromey at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-18772-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).