This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug server/17147] with gdbserver + all-stop + async, can't quit gdb because target is running
- From: "xdje42 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 15 Jul 2014 15:52:41 +0000
- Subject: [Bug server/17147] with gdbserver + all-stop + async, can't quit gdb because target is running
- Auto-submitted: auto-generated
- References: <bug-17147-4717 at http dot sourceware dot 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.