caio/clang-p2996
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Even when we aren’t going to init all the lldb.frame, etc, globals, init lldb.debugger, since each script interpreter is tied to just one debugger.

Browse Source 
llvm-svn: 169663
This commit is contained in:
Jim Ingham
2012-12-08 02:02:04 +00:00
parent 593f993a68
commit 5320624dfd
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
lldb/source/Interpreter/ScriptInterpreterPython.cpp
View File

@@ -624,6 +624,13 @@ ScriptInterpreterPython::EnterSession (bool init_lldb_globals)
run_string.PutCString ("; lldb.frame = lldb.thread.GetSelectedFrame ()");
run_string.PutCString ("')");
}
else
{
// If we aren't initing the globals, we should still always set the debugger (since that is always unique.)
run_string.Printf ( "run_one_line (%s, \"lldb.debugger_unique_id = %" PRIu64, m_dictionary_name.c_str(), GetCommandInterpreter().GetDebugger().GetID());
run_string.Printf ( "; lldb.debugger = lldb.SBDebugger.FindDebuggerWithID (%" PRIu64 ")", GetCommandInterpreter().GetDebugger().GetID());
run_string.PutCString ("\")");
}
PyRun_SimpleString (run_string.GetData());
run_string.Clear();