aboutsummaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorMatheus Tavares Bernardino <quic_mathbern@quicinc.com>2023-05-04 12:37:31 -0300
committerTaylor Simpson <tsimpson@quicinc.com>2023-05-18 12:40:52 -0700
commit758370052fb602f9f23c3b8ae26a6133373c78e6 (patch)
tree6953d7d93c67618e73669f4b6102ebb99d10b6a4 /tests
parent9e6d4938d106ca775108ec2a1fecc6d789543088 (diff)
downloadqemu-758370052fb602f9f23c3b8ae26a6133373c78e6.zip
qemu-758370052fb602f9f23c3b8ae26a6133373c78e6.tar.gz
qemu-758370052fb602f9f23c3b8ae26a6133373c78e6.tar.bz2
gdbstub: only send stop-reply packets when allowed to
GDB's remote serial protocol allows stop-reply messages to be sent by the stub either as a notification packet or as a reply to a GDB command (provided that the cmd accepts such a response). QEMU currently does not implement notification packets, so it should only send stop-replies synchronously and when requested. Nevertheless, it still issues unsolicited stop messages through gdb_vm_state_change(). Although this behavior doesn't seem to cause problems with GDB itself (the messages are just ignored), it can impact other debuggers that implement the GDB remote serial protocol, like hexagon-lldb. Let's change the gdbstub to send stop messages only as a response to a previous GDB command that accepts such a reply. Signed-off-by: Matheus Tavares Bernardino <quic_mathbern@quicinc.com> Acked-by: Alex Bennée <alex.bennee@linaro.org> Signed-off-by: Taylor Simpson <tsimpson@quicinc.com> Message-Id: <a49c0897fc22a6a7827c8dfc32aef2e1d933ec6b.1683214375.git.quic_mathbern@quicinc.com>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions