summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/gdb-remote
diff options
context:
space:
mode:
authorGreg Clayton <gclayton@apple.com>2012-07-02 22:05:25 +0000
committerGreg Clayton <gclayton@apple.com>2012-07-02 22:05:25 +0000
commit1f5181aa45d4d65901e56befe953d9b307e8179f (patch)
treeb29e9846d2149fa78593ef844bd6d998e7932dd0 /lldb/source/Plugins/Process/gdb-remote
parentc4a6e515969a3f62100673cf4d400eaee0d9df82 (diff)
downloadbcm5719-llvm-1f5181aa45d4d65901e56befe953d9b307e8179f.tar.gz
bcm5719-llvm-1f5181aa45d4d65901e56befe953d9b307e8179f.zip
<rdar://problem/11744001>
Fixed an issue where GDB servers that don't support the thread suffix could get registers states incorrectly due to an incorrect assumption that the current register thread (set using the "Hg%x" packet) will always be cached between runs. Now we clear the cached register thred when the process is resumed. llvm-svn: 159603
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote')
-rw-r--r--lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
index cf527e26283..83d2843309a 100644
--- a/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
+++ b/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
@@ -381,6 +381,7 @@ GDBRemoteCommunicationClient::SendContinuePacketAndWaitForResponse
StringExtractorGDBRemote &response
)
{
+ m_curr_tid = LLDB_INVALID_THREAD_ID;
LogSP log (ProcessGDBRemoteLog::GetLogIfAllCategoriesSet (GDBR_LOG_PROCESS));
if (log)
log->Printf ("GDBRemoteCommunicationClient::%s ()", __FUNCTION__);
OpenPOWER on IntegriCloud