<rdar://problem/13697881>

Fixed the GDB remote with the python OS plug-in to not show core threads when they aren't desired and also to have the threads "to the right thing" when continuing.

llvm-svn: 179912

1 files changed, 3 insertions, 3 deletions

diff --git a/lldb/source/Plugins/Process/Utility/ThreadMemory.cpp b/lldb/source/Plugins/Process/Utility/ThreadMemory.cpp
index e7602b89020..62c6aeb9c75 100644
--- a/lldb/source/Plugins/Process/Utility/ThreadMemory.cpp
+++ b/lldb/source/Plugins/Process/Utility/ThreadMemory.cpp
@@ -57,10 +57,10 @@ bool
 ThreadMemory::WillResume (StateType resume_state)
 {
     ClearStackFrames();
-    // Call the Thread::WillResume first. If we stop at a signal, the stop info
-    // class for signal will set the resume signal that we need below. The signal
-    // stuff obeys the Process::UnixSignal defaults. 
     Thread::WillResume(resume_state);
+
+    if (m_backing_thread_sp)
+        return m_backing_thread_sp->WillResume(resume_state);
     return true;
 }