summaryrefslogtreecommitdiffstats
path: root/lldb/source/Breakpoint
diff options
context:
space:
mode:
authorGreg Clayton <gclayton@apple.com>2013-11-05 23:28:00 +0000
committerGreg Clayton <gclayton@apple.com>2013-11-05 23:28:00 +0000
commit095eeaa0250161c3912f07c4c43ddb2a00a91faf (patch)
tree5750b5eef2aba484d7a513203d7575a89eb999ae /lldb/source/Breakpoint
parent5ede5cc9ba0293bf0764e83cc264c40920bf1d7d (diff)
downloadbcm5719-llvm-095eeaa0250161c3912f07c4c43ddb2a00a91faf.tar.gz
bcm5719-llvm-095eeaa0250161c3912f07c4c43ddb2a00a91faf.zip
<rdar://problem/15367122>
Fixed the test case for "test/functionalities/exec/TestExec.py" on Darwin. The issue was breakpoints were persisting and causing problems. When we exec, we need to clear out the process and target and start fresh with nothing and let the breakpoints populate themselves again. This patch correctly clears out the breakpoints and also flushes the process so that the objects (process/thread/frame) give out valid information. llvm-svn: 194106
Diffstat (limited to 'lldb/source/Breakpoint')
-rw-r--r--lldb/source/Breakpoint/BreakpointList.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/lldb/source/Breakpoint/BreakpointList.cpp b/lldb/source/Breakpoint/BreakpointList.cpp
index 5926663af7b..c6030d60ca0 100644
--- a/lldb/source/Breakpoint/BreakpointList.cpp
+++ b/lldb/source/Breakpoint/BreakpointList.cpp
@@ -204,13 +204,13 @@ BreakpointList::GetBreakpointAtIndex (size_t i) const
}
void
-BreakpointList::UpdateBreakpoints (ModuleList& module_list, bool added)
+BreakpointList::UpdateBreakpoints (ModuleList& module_list, bool added, bool delete_locations)
{
Mutex::Locker locker(m_mutex);
bp_collection::iterator end = m_breakpoints.end();
bp_collection::iterator pos;
for (pos = m_breakpoints.begin(); pos != end; ++pos)
- (*pos)->ModulesChanged (module_list, added);
+ (*pos)->ModulesChanged (module_list, added, delete_locations);
}
OpenPOWER on IntegriCloud