LLDB only uses the python interpreter stored in
"g:vebugger_path_python_lldb" Updated the documentation to explain why a special python variable is needed for LLDB
This commit is contained in:
parent
f5682be0e0
commit
c7304dc1f1
@ -1,7 +1,7 @@
|
||||
let s:script_dir_path=expand('<sfile>:p:h')
|
||||
|
||||
function! vebugger#lldb#start(binaryFile,args)
|
||||
let l:debuggerExe=vebugger#util#getToolFullPath('python',get(a:args,'version'),'python2')
|
||||
let l:debuggerExe=vebugger#util#getToolFullPath('python','lldb','python2')
|
||||
let l:debugger=vebugger#std#startDebugger(shellescape(l:debuggerExe)
|
||||
\.' '.s:script_dir_path.'/lldb_wrapper.py '.fnameescape(a:binaryFile))
|
||||
|
||||
|
@ -89,15 +89,20 @@ Notice that for LLDB, PDB and RDebug you use "python_lldb", "python" and
|
||||
(LLDB is called by a python wrapper because the LLDB executable has no
|
||||
machine interface like GDB to interact with).
|
||||
|
||||
You can set multiple versions for each debugger, by appending the version name
|
||||
to the debugger name with "_". These versions will be used when the "version"
|
||||
argument is supplied when running the debugger:
|
||||
You can set multiple versions for each debugger (except LLDB), by appending
|
||||
the version name to the debugger name with "_". These versions will be used
|
||||
when the "version" argument is supplied when running the debugger:
|
||||
|
||||
*g:vebugger_path_python_2* defaults to "python2"
|
||||
*g:vebugger_path_python_3* defaults to "python3"
|
||||
*g:vebugger_path_mdbg_32* No default - use it for the 32bit version of Mdbg
|
||||
*g:vebugger_path_mdbg_64* No default - use it for the 64bit version of Mdbg
|
||||
|
||||
For LLDB a special python variable is needed ("g:vebugger_path_python_lldb")
|
||||
since the lldb python api is only python 2 compatible. So, it is possible to
|
||||
use a python 2 interpreter for LLDB and another python version for PDB at
|
||||
the same time.
|
||||
|
||||
When stepping into functions in unopened files, they are opened with :new by
|
||||
default. This can be configured by setting *g:vebugger_view_source_cmd*
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user