public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug remote/18772] gdb does not respond to CTRL-C Date: Sun, 27 Nov 2022 09:31:56 +0000 [thread overview] Message-ID: <bug-18772-4717-8L4tvZbKAQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18772-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18772 --- Comment #16 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4c35c4c6a779c79e456b7a5311f74aafc9026bd5 commit 4c35c4c6a779c79e456b7a5311f74aafc9026bd5 Author: Tom de Vries <tdevries@suse.de> Date: Sun Nov 27 10:31:50 2022 +0100 [gdb/server] Emit warning for SIGINT failure Consider the executable from test-case gdb.base/interrupt-daemon.exp. When starting it using gdbserver: ... $ ./build/gdbserver/gdbserver localhost:2345 \ ./outputs/gdb.base/interrupt-daemon/interrupt-daemon ... and connecting to it using gdb: ... $ gdb -q -ex "target remote localhost:2345" \ -ex "set follow-fork-mode child" \ -ex "break daemon_main" -ex cont ... we are setup to do the same as in the test-case: interrupt a running inferior using ^C. So let's try: ... (gdb) continue Continuing. ^C ... After pressing ^C, nothing happens. This a known problem, filed as PR remote/18772. The problem is that in linux_process_target::request_interrupt, a kill is used to send a SIGINT, but it fails. And it fails silently. Make the failure verbose by adding a warning, such that the gdbserver output becomes more helpful: ... Process interrupt-daemon created; pid = 15068 Listening on port 2345 Remote debugging from host ::1, port 35148 Detaching from process 15068 Detaching from process 15085 gdbserver: Sending SIGINT to process group of pid 15068 failed: \ No such process ... Note that the failure can easily be reproduced using the test-case and target board native-gdbserver: ... (gdb) continue^M Continuing.^M PASS: gdb.base/interrupt-daemon.exp: fg: continue ^CFAIL: gdb.base/interrupt-daemon.exp: fg: ctrl-c stops process (timeout) ... as reported in PR server/23382. Tested on x86_64-linux. Approved-By: Simon Marchi <simon.marchi@efficios.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-27 9:32 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-05 11:32 [Bug remote/18772] New: " moorel at ntlworld dot com 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 [this message] 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-8L4tvZbKAQ@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).