Enrico Granata b4675a4e12 <rdar://problem/14266411> ... 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		2013-06-25 23:43:28 +00:00
..
interface	<rdar://problem/14266411>	2013-06-25 23:43:28 +00:00
build-swig-Python.sh	Change the SWIG wrappers to stop directly casting SB object to SWIG objects, and instead use a safer type-checked API (thanks templates)	2013-06-21 18:57:30 +00:00
edit-swig-python-wrapper-file.py	Fix remaining Python issues leftover from my previous patch.	2011-06-01 02:33:12 +00:00
finish-swig-Python-LLDB.sh	Adding a diagnose-nsstring command	2013-05-30 23:36:47 +00:00
modify-python-lldb.py	Make sure that the lldb globals:	2012-12-10 19:18:23 +00:00
python-extensions.swig	Implemented a types.py module that allows types to be inspected for padding.	2013-06-19 21:50:28 +00:00
python-swigsafecast.swig	Lots of cleanup on the SWIG wrapping layer	2013-06-21 23:27:16 +00:00
python-typemaps.swig	Sort out a number of mismatched integer types in order to cut down the number of compiler warnings.	2013-06-19 19:04:53 +00:00
python-wrapper.swig	<rdar://problem/14266411>	2013-06-25 23:43:28 +00:00