forked from OSchip/llvm-project
165545c7a4
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 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| GDBRemoteClientBaseTest.cpp | ||
| GDBRemoteCommunicationClientTest.cpp | ||
| GDBRemoteCommunicationServerLLGSTest.cpp | ||
| GDBRemoteCommunicationServerTest.cpp | ||
| GDBRemoteCommunicationTest.cpp | ||
| GDBRemoteTestUtils.cpp | ||
| GDBRemoteTestUtils.h | ||
| PortMapTest.cpp | ||