maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Added a warning about using the lldb.target, etc. for anything other than convenience when using the 

script command.

llvm-svn: 170014
This commit is contained in:
Jim Ingham 2012-12-12 20:23:52 +00:00
parent eb17816bf4
commit bd15897f35
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
lldb/www/python-reference.html
View File

@ -96,10 +96,14 @@ Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
<p>This drops you into the embedded python interpreter. When running under the <b>script</b> command,
lldb sets some convenience variables that give you quick access to the currently selected entities that characterize
the program and debugger state. In each case, if there is no currently selected entity of the appropriate
type, the variable's <b>IsValid</b> method will return false.
type, the variable's <b>IsValid</b> method will return false.
<p>Note also, these variables hold the values
of the selected objects on entry to the embedded interpreter. They do not update as you use the LLDB
API's to change, for example, the currently selected stack frame or thread.</p>
API's to change, for example, the currently selected stack frame or thread.
<p>As a corollary to this, because they get reset every time the script interpreter is entered, you should not
use these variables in general purpose python code that you write using the lldb module. After all, lldb can
run in a multithreaded environment, and another thread might call the "script" command, changing the value out
from under you.</p>
These are all global variables contained in the <b>lldb</b> python namespace :</p>
<table class="stats" width="620" cellspacing="0">
<tr>