b4675a4e12
The semi-unofficial way of returning a status from a Python command was to return a string (e.g. return "no such variable was found") that LLDB would pick as a clue of an error having happened
This checkin changes that:
- SBCommandReturnObject now exports a SetError() call, which can take an SBError or a plain C-string
- script commands now drop any return value and expect the SBCommandReturnObject ("return object") to be filled in appropriately - if you do nothing, a success will be assumed
If your commands were relying on returning a value and having LLDB pick that up as an error, please change your commands to SetError() through the return object or expect changes in behavior
llvm-svn: 184893
33 lines
1.0 KiB
Python
33 lines
1.0 KiB
Python
import sys
|
|
|
|
def welcome_impl(debugger, args, result, dict):
|
|
"""
|
|
Just a docstring for welcome_impl
|
|
A command that says hello to LLDB users
|
|
"""
|
|
print >>result, ('Hello ' + args + ', welcome to LLDB');
|
|
return None;
|
|
|
|
def target_name_impl(debugger, args, result, dict):
|
|
target = debugger.GetSelectedTarget()
|
|
file = target.GetExecutable()
|
|
print >>result, ('Current target ' + file.GetFilename())
|
|
if args == 'fail':
|
|
result.SetError('a test for error in command')
|
|
|
|
def print_wait_impl(debugger, args, result, dict):
|
|
result.SetImmediateOutputFile(sys.stdout)
|
|
print >>result, ('Trying to do long task..')
|
|
import time
|
|
time.sleep(1)
|
|
print >>result, ('Still doing long task..')
|
|
time.sleep(1)
|
|
print >>result, ('Done; if you saw the delays I am doing OK')
|
|
|
|
def check_for_synchro(debugger, args, result, dict):
|
|
if debugger.GetAsync() == True:
|
|
print >>result, ('I am running async')
|
|
if debugger.GetAsync() == False:
|
|
print >>result, ('I am running sync')
|
|
|