From 5d88a068eed8625b9668db9f6b254ae5d2a0e187 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Tue, 16 Oct 2012 00:09:33 +0000 Subject: Patch from Matt Kopec to fix the problem that if two breakpoints were set on consecutive addresses, the continue from the first breakpoint would skip the second. llvm-svn: 166000 --- lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp | 3 +++ 1 file changed, 3 insertions(+) (limited to 'lldb/source/Plugins/Process/gdb-remote') diff --git a/lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp b/lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp index b63b42d1ab0..36fa418cf2b 100644 --- a/lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp +++ b/lldb/source/Plugins/Process/gdb-remote/ThreadGDBRemote.cpp @@ -225,6 +225,9 @@ ThreadGDBRemote::GetPrivateStopReason () if (m_thread_stop_reason_stop_id != process_stop_id || (m_actual_stop_info_sp && !m_actual_stop_info_sp->IsValid())) { + if (IsStillAtLastBreakpointHit()) + return m_actual_stop_info_sp; + // If GetGDBProcess().SetThreadStopInfo() doesn't find a stop reason // for this thread, then m_actual_stop_info_sp will not ever contain // a valid stop reason and the "m_actual_stop_info_sp->IsValid() == false" -- cgit v1.2.3