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: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 17 Jul 2014 16:38:26 +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
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at google dot com
--- Comment #6 from dje at google dot com ---
I think a doc update is also required.
The doc refers to execution commands only, however with gdbserver one can't
even do things like "info threads" until the target stops.
---snip---
Background execution is especially useful in conjunction with non-stop
mode for debugging programs with multiple threads; see @ref{Non-Stop Mode}.
However, you can also use these commands in the normal all-stop mode with
the restriction that you cannot issue another execution command until the
previous one finishes. Examples of commands that are valid in all-stop
mode while the program is running include @code{help} and @code{info break}.
---snip---
--
You are receiving this mail because:
You are on the CC list for the bug.