llvm-project/lldb/scripts/Python
Jim Ingham 6fbc48bc42 This patch does a couple of things.
It completes the job of using EvaluateExpressionOptions consistently throughout
the inferior function calling mechanism in lldb begun in Greg's patch r194009. 

It removes a handful of alternate calls into the ClangUserExpression/ClangFunction/ThreadPlanCallFunction which
were there for convenience.  Using the EvaluateExpressionOptions removes the need for them.

Using that it gets the --debug option from Greg's patch to work cleanly.

It also adds another EvaluateExpressionOption to not trap exceptions when running expressions.  You shouldn't
use this option unless you KNOW your expression can't throw beyond itself.  This is:

<rdar://problem/15374885>

At present this is only available through the SB API's or python.

It fixes a bug where function calls would unset the ObjC & C++ exception breakpoints without checking whether
they were set by somebody else already.

llvm-svn: 194182
2013-11-07 00:11:47 +00:00
..
interface This patch does a couple of things. 2013-11-07 00:11:47 +00:00
build-swig-Python.sh Added a way to extract the module specifications from a file. A module specification is information that is required to describe a module (executable, shared library, object file, ect). This information includes host path, platform path (remote path), symbol file path, UUID, object name (for objects in .a files for example you could have an object name of "foo.o"), and target triple. Module specification can be used to create a module, or used to add a module to a target. A list of module specifications can be used to enumerate objects in container objects (like universal mach files and BSD archive files). 2013-07-08 22:22:41 +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 Added a way to extract the module specifications from a file. A module specification is information that is required to describe a module (executable, shared library, object file, ect). This information includes host path, platform path (remote path), symbol file path, UUID, object name (for objects in .a files for example you could have an object name of "foo.o"), and target triple. Module specification can be used to create a module, or used to add a module to a target. A list of module specifications can be used to enumerate objects in container objects (like universal mach files and BSD archive files). 2013-07-08 22:22:41 +00:00
python-swigsafecast.swig Second attempt at getting the PyCallable changes in trunk 2013-07-09 20:14:26 +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 Roll back the changes I made in r193907 which created a new Frame 2013-11-04 09:33:30 +00:00