aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp
diff options
context:
space:
mode:
authoreleviant <56861949+eleviant@users.noreply.github.com>2025-06-25 13:38:37 +0200
committerGitHub <noreply@github.com>2025-06-25 13:38:37 +0200
commitc941bee75d252ac9a9787dd0594959d890ddb073 (patch)
tree5fe5f945c5e0a23f58afbb6f4f756a8460295b7e /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp
parent97fdc237ddda7565c7c902cc4fc764f73e70686b (diff)
downloadllvm-c941bee75d252ac9a9787dd0594959d890ddb073.zip
llvm-c941bee75d252ac9a9787dd0594959d890ddb073.tar.gz
llvm-c941bee75d252ac9a9787dd0594959d890ddb073.tar.bz2
[lldb] Fix qEcho message handling. (#145675)
This fixes issues found in e066f35c6981c720e3a7e5883efc40c861b3b7, which was later reverted. The problem was with "k" message which was sent with sync_on_timeout flag set to true, so lldb was waiting for response, which is currently not being sent by lldb-server. Not waiting for response at all seems to be not a solution, because on MAC OS X lldb waits for response from "k" to gracefully kill inferior.
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp')
-rw-r--r--lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp3
1 files changed, 2 insertions, 1 deletions
diff --git a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp
index bea2faf..2ca7099 100644
--- a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp
+++ b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp
@@ -355,8 +355,9 @@ GDBRemoteCommunication::WaitForPacketNoLock(StringExtractorGDBRemote &packet,
disconnected = true;
Disconnect();
}
+ } else {
+ timed_out = true;
}
- timed_out = true;
break;
case eConnectionStatusSuccess:
// printf ("status = success but error = %s\n",