diff options
| author | Alex Bennée <alex.bennee@linaro.org> | 2020-12-23 16:36:16 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@polymtl.ca> | 2020-12-23 16:36:48 -0500 |
| commit | f37059ea22267e5b426df1732a2ae7ab45b1d848 (patch) | |
| tree | a230e9e3978cb121e9875cd54ae6a23a98b0ea40 /gdb | |
| parent | 279d901e5a7a16eb9a3383e316ff4a8d7473d6bd (diff) | |
| download | fsf-binutils-gdb-f37059ea22267e5b426df1732a2ae7ab45b1d848.zip fsf-binutils-gdb-f37059ea22267e5b426df1732a2ae7ab45b1d848.tar.gz fsf-binutils-gdb-f37059ea22267e5b426df1732a2ae7ab45b1d848.tar.bz2 | |
Clarify language for the '?' packet
Both QEMU and kgdb make the assumption that the '?' packet is only
sent during the initial setup of a gdbstub connection. Both use that
knowledge to reset breakpoints and ensure the gdbstub is in a
clean-state on a resumed connection. This can cause confusion for
others implementing clients that speak to gdbstub devices. To avoid
that make the language clearer that this is a start-up query packet
that you only expect to see once.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
gdb/doc/ChangeLog:
* gdb.texinfo (Packets): Clarify language for ? packet.
Change-Id: Iae25d3110fe28b8d2467704962a6889e55224ca5
Diffstat (limited to 'gdb')
| -rw-r--r-- | gdb/doc/ChangeLog | 4 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 7 |
2 files changed, 8 insertions, 3 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index d56cec2..1d88c92 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2020-12-23 Alex Bennée <alex.bennee@linaro.org> + + * gdb.texinfo (Packets): Clarify language for ? packet. + 2020-12-21 Joel Brobecker <brobecker@adacore.com> * gdb.texinfo (Requirements): Add GMP to list of requirements. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 617a364..93e7228 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -39502,9 +39502,10 @@ The remote target both supports and has enabled extended mode. @item ? @cindex @samp{?} packet @anchor{? packet} -Indicate the reason the target halted. The reply is the same as for -step and continue. This packet has a special interpretation when the -target is in non-stop mode; see @ref{Remote Non-Stop}. +This is sent when connection is first established to query the reason +the target halted. The reply is the same as for step and continue. +This packet has a special interpretation when the target is in +non-stop mode; see @ref{Remote Non-Stop}. Reply: @xref{Stop Reply Packets}, for the reply specifications. |