summaryrefslogtreecommitdiffstats
path: root/lldb/source/Target/Process.cpp
diff options
context:
space:
mode:
authorGreg Clayton <gclayton@apple.com>2013-05-21 21:55:59 +0000
committerGreg Clayton <gclayton@apple.com>2013-05-21 21:55:59 +0000
commit8cda7f083069d4cc1c8e5c8e658bbdbac0eea249 (patch)
treeea5530993e794203cb173e87ed617ab1651acde1 /lldb/source/Target/Process.cpp
parent4df05caadbbf588406f99ef74342db49a647c1e2 (diff)
downloadbcm5719-llvm-8cda7f083069d4cc1c8e5c8e658bbdbac0eea249.tar.gz
bcm5719-llvm-8cda7f083069d4cc1c8e5c8e658bbdbac0eea249.zip
Added a test case that verifies that LLDB can debug across a process exec'ing itself into a new program. This currently is only enabled for Darwin since we exec from 64 bit to 32 bit and vice versa for 'x86_64' targets.
This can easily be adapted for linux and other platforms, but I didn't want to break any buildbots by assuming it will work. llvm-svn: 182428
Diffstat (limited to 'lldb/source/Target/Process.cpp')
-rw-r--r--lldb/source/Target/Process.cpp2
1 files changed, 0 insertions, 2 deletions
diff --git a/lldb/source/Target/Process.cpp b/lldb/source/Target/Process.cpp
index b86b140dff4..5ed9a68bdb4 100644
--- a/lldb/source/Target/Process.cpp
+++ b/lldb/source/Target/Process.cpp
@@ -5588,8 +5588,6 @@ Process::DidExec ()
m_allocated_memory_cache.Clear();
m_language_runtimes.clear();
m_thread_list.DiscardThreadPlans();
- m_thread_list.Clear();
- m_thread_list_real.Clear();
m_memory_cache.Clear(true);
DoDidExec();
CompleteAttach ();
OpenPOWER on IntegriCloud