Correct an error in the remote protocol specification

The list of commands that a stub must implement was wrong.

gdb/ChangeLog:
2020-07-22  Reuben Thomas  <rrt@sc3d.org>

	* gdb.texinfo (Remote Protocol, Overview): Correct the description
	of which remote protocol commands are mandatory for a stub to
	implement.
This commit is contained in:
Reuben Thomas 2020-07-22 16:15:29 +01:00 committed by Pedro Alves
parent a67a1c41fe
commit c9fe1b583c
2 changed files with 13 additions and 4 deletions

View file

@ -1,3 +1,9 @@
2020-07-22 Reuben Thomas <rrt@sc3d.org>
* gdb.texinfo (Remote Protocol, Overview): Correct the description
of which remote protocol commands are mandatory for a stub to
implement.
2020-07-20 Ludovic Courtès <ludo@gnu.org>
* doc/guile.texi (Guile Introduction): Mention Guile 3.0.

View file

@ -39134,12 +39134,15 @@ For any @var{command} not supported by the stub, an empty response
protocol. A newer @value{GDBN} can tell if a packet is supported based
on that response.
At a minimum, a stub is required to support the @samp{g} and @samp{G}
At a minimum, a stub is required to support the @samp{?} command to
tell @value{GDBN} the reason for halting, @samp{g} and @samp{G}
commands for register access, and the @samp{m} and @samp{M} commands
for memory access. Stubs that only control single-threaded targets
can implement run control with the @samp{c} (continue), and @samp{s}
(step) commands. Stubs that support multi-threading targets should
support the @samp{vCont} command. All other commands are optional.
can implement run control with the @samp{c} (continue) command, and if
the target architecture supports hardware-assisted single-stepping,
the @samp{s} (step) command. Stubs that support multi-threading
targets should support the @samp{vCont} command. All other commands
are optional.
@node Packets
@section Packets