public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16809] interrupt -a Date: Tue, 15 Jul 2014 19:59:00 -0000 [thread overview] Message-ID: <bug-16809-4717-UUSIfx58VX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16809-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16809 --- Comment #12 from Doug Evans <xdje42 at gmail dot com> --- (In reply to Doug Evans from comment #11) > What should happen is that "interrupt" or "interrupt -a" without an "&" > should operate synchronously and not print the gdb prompt until the command > has succeeded (just like commands that resume the inferior like run, s/succeeded/completed/ > continue, etc.). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-15 19:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-04 20:00 [Bug gdb/16809] New: " dilyan.palauzov at aegee dot org 2014-07-12 19:02 ` [Bug gdb/16809] " xdje42 at gmail dot com 2014-07-13 21:58 ` dilyan.palauzov at aegee dot org 2014-07-13 23:30 ` dilyan.palauzov at aegee dot org 2014-07-14 0:19 ` xdje42 at gmail dot com 2014-07-14 0:30 ` xdje42 at gmail dot com 2014-07-14 0:51 ` xdje42 at gmail dot com 2014-07-14 3:10 ` xdje42 at gmail dot com 2014-07-15 6:18 ` dje at google dot com 2014-07-15 8:19 ` palves at redhat dot com 2014-07-15 19:48 ` dilyan.palauzov at aegee dot org 2014-07-15 19:58 ` xdje42 at gmail dot com 2014-07-15 19:59 ` xdje42 at gmail dot com [this message] 2014-07-15 21:21 ` palves at redhat dot com
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-16809-4717-UUSIfx58VX@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).