aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdb_obstack.h
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2017-05-15 10:11:57 +0100
committerAndrew Burgess <andrew.burgess@embecosm.com>2017-05-22 20:31:11 +0100
commit176efed15cabb932a7e9fb2c5e6ef0753e8351a0 (patch)
tree984dcdd9d885989bb22da7c39683f4247340ef5b /gdb/gdb_obstack.h
parent04ef582ace91cad765d056cc95624478e0421144 (diff)
downloadbinutils-176efed15cabb932a7e9fb2c5e6ef0753e8351a0.zip
binutils-176efed15cabb932a7e9fb2c5e6ef0753e8351a0.tar.gz
binutils-176efed15cabb932a7e9fb2c5e6ef0753e8351a0.tar.bz2
gdb: Document vMustReplyEmpty remote packet
Add mention of the vMustReplyEmpty to the remote serial protocol documentation. It is important that this packet be treated in the same fashion as any other unknown 'v' packet, and I have tried to reflect this in the description of the packet, it is not simply the case that we _must_ return the empty string for this packet. As the intention is that we should treat this packet as unknown then an argument could be made that we should not document it, however, for someone implementing a gdbserver from scratch, seeing an undocumented packet arrive from gdb is confusing, and will probably cause them to have to read the code in order to check how this packet should be handled, which is not ideal. gdb/doc/ChangeLog: * gdb.texinfo (Packets): Document vMustReplyEmpty packet.
Diffstat (limited to 'gdb/gdb_obstack.h')
0 files changed, 0 insertions, 0 deletions