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 gdb/17160] treat "interrupt -a" like "interrupt" in all-stop mode Date: Tue, 14 Jun 2022 15:04:21 +0000 [thread overview] Message-ID: <bug-17160-4717-0mvXvshi0r@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17160-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17160 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=edb6b77c755545afb969fcebfa900b07a4b93c94 commit edb6b77c755545afb969fcebfa900b07a4b93c94 Author: Tom Tromey <tromey@adacore.com> Date: Wed Jun 8 09:26:08 2022 -0600 Allow 'interrupt -a' in all-stop mode PR gdb/17160 points out that "interrupt -a" errors in all-stop mode, but there's no good reason for this. This patch removes the error. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=17160 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-14 15:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-15 15:51 [Bug gdb/17160] New: " xdje42 at gmail dot com 2014-07-15 19:14 ` [Bug gdb/17160] " palves at redhat dot com 2015-04-29 19:48 ` simon.marchi at ericsson dot com 2022-06-08 15:28 ` tromey at sourceware dot org 2022-06-14 15:04 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-14 15:04 ` 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-17160-4717-0mvXvshi0r@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).