summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python/build-swig-Python.sh
Commit message (Collapse)AuthorAgeFilesLines
* Update comments.Johnny Chen2011-04-291-1/+1
| | | | llvm-svn: 130533
* Move the iteration protocol of lldb objects to the auto-generated lldb ↵Johnny Chen2011-04-281-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | Python module. This is so that the objects which support the iteration protocol are immediately obvious from looking at the lldb.py file. SBTarget supports two types of iterations: module and breakpoint. For an SBTarget instance, you will need to issue either: for m in target.module_iter() or for b in target.breakpoint_iter() For other single iteration protocol objects, just use, for example: for thread in process: ID = thread.GetThreadID() for frame in thread: frame.Disassemble() .... llvm-svn: 130442
* Fixed the LLDB build so that we can have private types, private enums andGreg Clayton2011-03-241-1/+1
| | | | | | | | public types and public enums. This was done to keep the SWIG stuff from parsing all sorts of enums and types that weren't needed, and allows us to abstract our API better. llvm-svn: 128239
* Look for swig in /usr/bin and /usr/local/bin.Jim Ingham2011-03-011-1/+2
| | | | llvm-svn: 126732
* Remove references to particular Python version (use the system defaultCaroline Tice2010-10-281-0/+11
| | | | | | | | | | version); change include statements to use Python.h in the Python framework on Mac OS X systems; leave it using regular Python.h on other systems. Note: I think this *ought* to work properly on Linux systems, but I don't have a system to test it on... llvm-svn: 117612
* First pass at adding logging capabilities for the API functions. At the momentCaroline Tice2010-10-261-0/+18
| | | | | | | | | | | | | | | | | | it logs the function calls, their arguments and the return values. This is not complete or polished, but I am committing it now, at the request of someone who really wants to use it, even though it's not really done. It currently does not attempt to log all the functions, just the most important ones. I will be making further adjustments to the API logging code over the next few days/weeks. (Suggestions for improvements are welcome). Update the Python build scripts to re-build the swig C++ file whenever the python-extensions.swig file is modified. Correct the help for 'log enable' command (give it the correct number & type of arguments). llvm-svn: 117349
* Add header files that were added to lldb.swig to the buildCaroline Tice2010-10-181-0/+5
| | | | | | | script, so it can keep track of dependencies accurately (for knowing when to re-build LLDBWrapPython.cpp). llvm-svn: 116765
* Cleaned up the SWIG stuff so all includes happen as they should, no pullingGreg Clayton2010-10-071-2/+6
| | | | | | | | | | | | | | | | | | tricks to get types to resolve. I did this by correctly including the correct files: stdint.h and all lldb-*.h files first before including the API files. This allowed me to remove all of the hacks that were in the lldb.swig file and it also allows all of the #defines in lldb-defines.h and enumerations in lldb-enumerations.h to appear in the lldb.py module. This will make the python script code a lot more readable. Cleaned up the "process launch" command to not execute a "process continue" command, it now just does what it should have with the internal API calls instead of executing another command line command. Made the lldb_private::Process set the state to launching and attaching if WillLaunch/WillAttach return no error respectively. llvm-svn: 115902
* Added the ability to get the disassembly instructions from the function andGreg Clayton2010-10-061-0/+2
| | | | | | symbol. llvm-svn: 115734
* Remove SBCommandContext which was not needed or doing anything.Caroline Tice2010-09-221-2/+3
| | | | | | Add SBValueList.h & SBStream.h to build-swig-Python.sh; add SBValueList.h to lldb.swig llvm-svn: 114549
* o Exposed SBFileSpec to the Python APIs in lldb.py.Johnny Chen2010-08-271-0/+1
| | | | | | | | | | | o Fixed a crasher when getting it via SBTarget.GetExecutable(). >>> filespec = target.GetExecutable() Segmentation fault o And renamed SBFileSpec::GetFileName() to GetFilename() to be consistent with FileSpec::GetFilename(). llvm-svn: 112308
* o Added a test case for array_types which uses the Python APIs from lldb.py,Johnny Chen2010-08-261-2/+16
| | | | | | | | | | | | | with the only exception of launching the process from SBTarget which is under investigation. o build-swig-Python.sh should also checks the timestamp of ${swig_input_file} for update eligibility. Also, once an update is in order, there's no need to check the remaining header files for timestamps. o Coaches swig to treat StopReason as an int type, instead of a C++ class. llvm-svn: 112210
* Add a unique ID to each debugger instance.Caroline Tice2010-06-301-0/+7
| | | | | | | | | | | | | | | | | Add functions to look up debugger by id Add global variable to lldb python module, to hold debugger id Modify embedded Python interpreter to update the global variable with the id of its current debugger. Modify the char ** typemap definition in lldb.swig to accept 'None' (for NULL) as a valid value. The point of all this is so that, when you drop into the embedded interpreter from the command interpreter (or when doing Python-based breakpoint commands), there is a way for the Python side to find/get the correct debugger instance ( by checking debugger_unique_id, then calling SBDebugger::FindDebuggerWithID on it). llvm-svn: 107287
* Parameterize the shell scripts for creating and copying the python andCaroline Tice2010-06-161-53/+55
| | | | | | | | other script files around, so they can be run from outside Xcode. Also, check the current OS, and only try to use the framework structure stuff on Darwin systems. llvm-svn: 106132
* Initial checkin of lldb code from internal Apple repo.Chris Lattner2010-06-081-0/+127
llvm-svn: 105619
OpenPOWER on IntegriCloud