tree 4df0757907fee3c77ed6a3cb71fb4b1a6d75bcd0
parent 3a86a373c90c8ff2b692fbc8ce1a07be0f8ff486
author Pavel Labath <pavel@labath.sk> 1637749244 +0100
committer Copybara-Service <copybara-worker@google.com> 1637840762 -0800

[lldb/gdb-remote] Ignore spurious ACK packets

Although I cannot find any mention of this in the specification, both
gdb and lldb agree on sending an initial + packet after establishing the
connection.

OTOH, gdbserver and lldb-server behavior is subtly different. While
lldb-server *expects* the initial ack, and drops the connection if it is
not received, gdbserver will just ignore a spurious ack at _any_ point
in the connection.

This patch changes lldb's behavior to match that of gdb. An ACK packet
is ignored at any point in the connection (except when expecting an ACK
packet, of course). This is inline with the "be strict in what you
generate, and lenient in what you accept" philosophy, and also enables
us to remove some special cases from the server code. I've extended the
same handling to NAK (-) packets, mainly because I don't see a reason to
treat them differently here.

(The background here is that we had a stub which was sending spurious
+ packets. This bug has since been fixed, but I think this change makes
sense nonetheless.)

Differential Revision: https://reviews.llvm.org/D114520

GitOrigin-RevId: 165545c7a431aa3682fd9468014771c1c5228226