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 server/17147] with gdbserver + all-stop + async, can't quit gdb because target is running
Date: Tue, 15 Jul 2014 15:52:00 -0000	[thread overview]
Message-ID: <bug-17147-4717-M0FVaCj7vu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17147-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17147

--- Comment #4 from Doug Evans <xdje42 at gmail dot com> ---
One thought would be to print a message either with commands that resume the
inferior in the background, or with the "Cannot execute this command while the
target is running." error message.

E.g.

Cannot execute this command while the target is running.
Use the "interrupt" command to stop the target.

or perhaps a teensy bit better,

Cannot execute this command while the target is running.
Use the "interrupt" command to stop the target and then try again.

[side note: why does "interrupt -a" have to be an error in all-stop mode?
Instead just treat "interrupt -a" == "interrupt".  Filed bug 17160.]

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-07-15 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 17:01 [Bug server/17147] New: " xdje42 at gmail dot com
2014-07-12 18:17 ` [Bug server/17147] " xdje42 at gmail dot com
2014-07-15 11:36 ` palves at redhat dot com
2014-07-15 14:50 ` xdje42 at gmail dot com
2014-07-15 15:52 ` xdje42 at gmail dot com [this message]
2014-07-15 19:16 ` palves at redhat dot com
2014-07-17 16:38 ` dje at google dot com
2014-07-20 22:39 ` cvs-commit at gcc dot gnu.org
2014-07-20 22:44 ` cvs-commit at gcc dot gnu.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-17147-4717-M0FVaCj7vu@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: link
Be 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).