summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python
Commit message (Collapse)AuthorAgeFilesLines
* API cleanup.Greg Clayton2012-10-161-42/+19
| | | | llvm-svn: 166070
* Add the ability to set timeout & "run all threads" options both from the ↵Jim Ingham2012-10-164-0/+112
| | | | | | | | | | "expr" command and from the SB API's that evaluate expressions. <rdar://problem/12457211> llvm-svn: 166062
* Removing the two extra GetXSize(bool) calls since we do not desire to ↵Enrico Granata2012-10-161-6/+0
| | | | | | support them long-term llvm-svn: 166060
* <rdar://problem/12446320> Fixing an issue with our Driver where setting an ↵Enrico Granata2012-10-161-3/+15
| | | | | | immediate output would not cause suppression of the final printout. This allows effective output redirection for Python commands llvm-svn: 166058
* <rdar://problem/12490588>Greg Clayton2012-10-131-0/+3
| | | | | | From SBType, we can now get a lldb::BasicType enumeration out of an existing type. llvm-svn: 165857
* <rdar://problem/12490558>Greg Clayton2012-10-121-1/+1
| | | | | | SBProcess::SetSelectedThreadByID() had a "uint32_t tid" parameter which would truncate 64 bit thread IDs (lldb::tid_t is 64 bit). llvm-svn: 165852
* <rdar://problem/12462744> Implement a new SBDeclaration class to wrap an ↵Enrico Granata2012-10-104-0/+80
| | | | | | lldb_private::Declaration - make a GetDeclaration() API on SBValue to return a declaration. This will only work for vroot variables as they are they only objects for which we currently provide a valid Declaration llvm-svn: 165672
* Change the Thread constructor over to take a Process& rather than a ↵Jim Ingham2012-10-101-0/+12
| | | | | | | | | | | | | ProcessSP. We can't create Threads with a NULL ProcessSP, so it makes no sense to use the SP. Then make the Thread a Broadcaster, and get it to broadcast when the selected frame is changed (but only from the Command Line) and when Thread::ReturnFromFrame changes the stack. Made the Driver use this notification to print the new thread status rather than doing it in the command. Fixed a few places where people were setting their broadcaster class by hand rather than using the static broadcaster class call. <rdar://problem/12383087> llvm-svn: 165640
* Fix a build warning and a dangerous possible crasher.Greg Clayton2012-10-081-1/+1
| | | | llvm-svn: 165460
* <rdar://problem/12200505> Fixing a logical error in SBProcess, where the ↵Enrico Granata2012-10-081-2/+3
| | | | | | get_process_thread_list function was creating invalid threads_access instances, and hence failing to correctly fill in the list llvm-svn: 165421
* Silly me! There was a closing ) missing from one of the lines - and Python ↵Enrico Granata2012-10-081-1/+1
| | | | | | complained about syntax errors on the next line. It being a Friday afternoon made the rest llvm-svn: 165420
* Retrying to apply Vishal's patch - hopefully this time it won't break ↵Enrico Granata2012-10-081-12/+20
| | | | | | Jason's build llvm-svn: 165410
* Revert Vishal's patch that Enrico commited, at least for the weekend. With ↵Jason Molenda2012-10-061-20/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | it applied, starting lldb I get % ./lldb -x Traceback (most recent call last): File "<string>", line 1, in <module> File "/private/tmp/build/Debug/LLDB.framework/Versions/A/Resources/Python/lldb/__init__.py", line 9008 raise TypeError("No array item of type %s" % str(type(key))) ^ SyntaxError: invalid syntax Traceback (most recent call last): File "<string>", line 1, in <module> NameError: name 'run_one_line' is not defined Traceback (most recent call last): File "<string>", line 1, in <module> NameError: name 'run_one_line' is not defined Traceback (most recent call last): File "<string>", line 1, in <module> NameError: name 'run_one_line' is not defined (lldb) I did a clean build and still got the problem so I'm backing this out until Enrico can look at it. llvm-svn: 165356
* patch from Vishal Patel to improve our lldb.value wrapperEnrico Granata2012-10-061-11/+20
| | | | llvm-svn: 165348
* <rdar://problem/12442990> Fix the implementation of lldb.value.__eq__Enrico Granata2012-10-051-1/+9
| | | | llvm-svn: 165344
* Add one-shot breakpoints (-o option to "break set") and a tbreak alias for ↵Jim Ingham2012-10-051-0/+6
| | | | | | our gdb friends. llvm-svn: 165328
* <rdar://problem/12099999> renaming SBStream::Printf to Print in the ↵Enrico Granata2012-10-041-3/+9
| | | | | | scripting world in order to avoid supporting varargs through SWIG llvm-svn: 165274
* Implementing plugins that provide commands.Enrico Granata2012-09-283-1/+7
| | | | | | | | | | | | | | | | | | | This checkin adds the capability for LLDB to load plugins from external dylibs that can provide new commands It exports an SBCommand class from the public API layer, and a new SBCommandPluginInterface There is a minimal load-only plugin manager built into the debugger, which can be accessed via Debugger::LoadPlugin. Plugins are loaded from two locations at debugger startup (LLDB.framework/Resources/PlugIns and ~/Library/Application Support/LLDB/PlugIns) and more can be (re)loaded via the "plugin load" command For an example of how to make a plugin, refer to the fooplugin.cpp file in examples/plugins/commands Caveats: Currently, the new API objects and features are not exposed via Python. The new commands can only be "parsed" (i.e. not raw) and get their command line via a char** parameter (we do not expose our internal Args object) There is no unloading feature, which can potentially lead to leaks if you overwrite the commands by reloading the same or different plugins There is no API exposed for option parsing, which means you may need to use getopt or roll-your-own llvm-svn: 164865
* Patch from Dan Malea to get the Bourne shells scripts to run cleanly on ↵Jason Molenda2012-09-272-30/+30
| | | | | | Ubuntu. llvm-svn: 164801
* Add an API to figure out whether a breakpoint is internal or not.Jim Ingham2012-09-251-0/+3
| | | | llvm-svn: 164648
* Fixed some problems with SWIG bindings.Filipe Cabecinhas2012-09-142-11/+13
| | | | | | | | | | This may (but shouldn't) break Linux (but I tested and it still worked on FreeBSD). The same shell scripts are now used on Xcode and Makefiles, for generating the SWIG bindings. Some compatibility fixes were applied, too (python path, bash-isms, etc). llvm-svn: 163912
* Make the unwinding of the stack part of "thread return" work, and add the ↵Jim Ingham2012-09-141-1/+1
| | | | | | thread return command. llvm-svn: 163867
* Start at getting "thread return" working. Doesn't work yet.Jim Ingham2012-09-121-0/+3
| | | | llvm-svn: 163670
* Simplify the typecheck code.Filipe Cabecinhas2012-08-281-10/+4
| | | | llvm-svn: 162753
* Fixing a potential control may reach end of non-void function issueEnrico Granata2012-08-271-0/+1
| | | | llvm-svn: 162685
* Added SBDebugger's log callbacks to Python-landFilipe Cabecinhas2012-08-254-32/+91
| | | | | | | | | | | | | | | | | | | - Tweaked a parameter name in SBDebugger.h so my typemap will catch it; - Added a SBDebugger.Create(bool, callback, baton) to the swig interface; - Added SBDebugger.SetLoggingCallback to the swig interface; - Added a callback utility function for log callbacks; - Guard against Py_None on both callback utility functions; - Added a FIXME to the SBDebugger API test; - Added a __del__() stub for SBDebugger. We need to be able to get both the log callback and baton from an SBDebugger if we want to protect against memory leaks (or make the user responsible for holding another reference to the callback). Additionally, it's impossible to revert from a callback-backed log mechanism to a file-backed log mechanism. llvm-svn: 162633
* Fixing a bunch of issues with the OS plugin codeEnrico Granata2012-08-241-1/+1
| | | | llvm-svn: 162527
* Adding bindings to the Script Interpreter for some basic Python OS plugin ↵Enrico Granata2012-08-241-0/+97
| | | | | | functionality (still WIP) llvm-svn: 162513
* Fixed a Linux building bug pointed out by Daniel Malea.Filipe Cabecinhas2012-08-221-1/+1
| | | | llvm-svn: 162373
* Added a typemap and wrappers for SBInputReader callbacksFilipe Cabecinhas2012-08-223-1/+87
| | | | | | | | | | | | | | Now it's possible to use SBInputReader callbacks in Python. We leak the callback object, unfortunately. A __del__ method can be added to SBInputReader, but we have no way to check the callback function that is on the reader. So we can't call Py_DECREF on it when we have our PythonCallback function. One way to do it is to assume that reified SBInputReaders always have a Python callback (and always call Py_DECREF). Another one is to add methods or properties to SBInputReader (or make the m_callback_function property public). llvm-svn: 162356
* Fix a crash (_wrap_SBDebugger_SetInputFileHandle -> PyString_AsString) ↵Johnny Chen2012-08-201-2/+9
| | | | | | | | running the test suite. Also modify the boundary condition test case SBDebugger.DispatchInput(None) to be wrapped inside a try-except clause for now. llvm-svn: 162228
* A baton isn't needed to dispatch input.Filipe Cabecinhas2012-08-202-1/+17
| | | | | | I also added a typemap to make DispatchInput usable in Python. llvm-svn: 162204
* Add FILE* typemaps for SBDebugger.GetInputFileHandle() and friends.Filipe Cabecinhas2012-08-201-0/+35
| | | | llvm-svn: 162203
* Merge python-GIL bracnh (by filcab) back into trunk!Johnny Chen2012-08-181-1/+1
| | | | llvm-svn: 162161
* rdar://problem/11457143 [ER] need "watchpoint command ..."Johnny Chen2012-08-091-0/+79
| | | | | | Add 'watchpoint command add/delete/list' to lldb, plus two .py test files. llvm-svn: 161638
* <rdar://problem/11275622>Greg Clayton2012-07-311-1/+86
| | | | | | | | | | | | | | | | | | | | | | | | | Added new API to lldb::SBTypeMember for bitfields: bool SBTypeMember::IsBitfield(); uint32_t SBTypeMember::GetBitfieldSizeInBits(); Also added new properties for easy access. Now SBTypeMember objects in python have a "fields" property for all type fields, "bases" for all direct bases, "vbases" for all virtual base classes and "members" for a combo of all three organized by bit offset. They all return a python list() of SBTypeMember objects. Usage: (lldb) script >>> t = lldb.target.FindFirstType("my_type") >>> for field in t.fields: ... print field >>> for vbase in t.vbases: ... print vbase >>> for base in t.bases: ... print base >>> for member in t.members: ... print member Also added new "is_bitfield" property to the SBTypeMember objects that will return the result of SBTypeMember::IsBitfield(), and "bitfield_bit_size" which will return the result of SBTypeMember::GetBitfieldSizeInBits(); I also fixed "SBTypeMember::GetOffsetInBytes()" to return the correct byte offset. llvm-svn: 161091
* Added an lldb_private & equivalent SB API to send an AsyncInterrupt to the ↵Jim Ingham2012-07-271-0/+3
| | | | | | | | | | | | | | event loop. Convert from calling Halt in the lldb Driver.cpp's input reader's sigint handler to sending this AsyncInterrupt so it can be handled in the event loop. If you are attaching and get an async interrupt, abort the attach attempt. Also remember to destroy the process if get interrupted while attaching. Getting this to work also required handing the eBroadcastBitInterrupt in a few more places in Process WaitForEvent & friends. <rdar://problem/10792425> llvm-svn: 160903
* Add "vAttachOrWait" to debugserver, so you can implement "attach to the ↵Jim Ingham2012-07-201-0/+6
| | | | | | process if it exists OR wait for it" without race conditions. Use that in lldb. llvm-svn: 160578
* Add accessors on process to get & set the selected thread by IndexID (useful ↵Jim Ingham2012-07-132-0/+27
| | | | | | since that's the one that "thread list" shows and it won't get reused even if the underlying system thread ID gets reused. llvm-svn: 160187
* Added documentation for many of our python properties and also made the ↵Greg Clayton2012-06-2927-238/+239
| | | | | | property help show up by declaring the properties correctly. We previosly declared properties into a local "x" variable, what I didn't realize is that the help will use this as the property name for the help output. llvm-svn: 159468
* Added the ability to read the dSYM plist file with source remappings even ↵Greg Clayton2012-06-271-0/+3
| | | | | | | | when DebugSymbols isn't used to find the dSYM. We now parse the plist as XML in the MacOSX symbol vendor. Added the ability to get a section load address given a target which is needed for a previous checking which saves crashlogs. llvm-svn: 159298
* Modify the ranges_access() helper function to be able to lookup the address ↵Greg Clayton2012-06-271-0/+4
| | | | | | | | range in a block given an address. Since blocks can have multiple discontiguous ranges, it helps to be able to get the current address range for the current block in a frame. This can be used in code like: curr_block_range = lldb.frame.block.range[lldb.frame.addr] llvm-svn: 159289
* Fixed the get_process_thread_list function to correctly return a list of all ↵Greg Clayton2012-06-271-1/+1
| | | | | | threads in a process. llvm-svn: 159288
* Make a way to set the result status for Python defined commands, and don't ↵Jim Ingham2012-06-271-0/+3
| | | | | | | | overwrite the status of the result if the python command has set it. llvm-svn: 159273
* Make raw & parsed commands subclasses of CommandObject rather than having ↵Jim Ingham2012-06-081-0/+3
| | | | | | | | | | | | | | | | the raw version implement an Execute which was never going to get run and another ExecuteRawCommandString. Took the knowledge of how to prepare raw & parsed commands out of CommandInterpreter and put it in CommandObject where it belongs. Also took all the cases where there were the subcommands of Multiword commands declared in the .h file for the overall command and moved them into the .cpp file. Made the CommandObject flags work for raw as well as parsed commands. Made "expr" use the flags so that it requires you to be paused to run "expr". llvm-svn: 158235
* rdar://problem/11584012Johnny Chen2012-06-043-6/+4
| | | | | | | | | | | Refactorings of watchpoint creation APIs so that SBTarget::WatchAddress(), SBValue::Watch(), and SBValue::WatchPointee() now take an additional 'SBError &error' parameter (at the end) to contain the reason if there is some failure in the operation. Update 'watchpoint set variable/expression' commands to take advantage of that. Update existing test cases to reflect the API change and add test cases to verify that the SBError mechanism works for SBTarget::WatchAddress() by passing an invalid watch_size. llvm-svn: 157964
* Fix the comments about LLDB_DISABLE_PYTHON in the python swig shell scripts ↵Jim Ingham2012-05-262-3/+8
| | | | | | to be more clear. llvm-svn: 157506
* Fix missing Resources/Python directory for macosx build.Johnny Chen2012-05-242-3/+3
| | | | llvm-svn: 157405
* Change the "Debug" build to use the current MacOSX SDK. Fix the swig ↵Jim Ingham2012-05-241-5/+6
| | | | | | | | builder to have an explicit short-circuit of the Python SWIG building, rather than relying on the SDKROOT being set. llvm-svn: 157363
* Add SBProcess::GetNumSupportedHardwareWatchpoints() API and export it ↵Johnny Chen2012-05-231-0/+3
| | | | | | | | through the Python scripting bridge. Add/modify some test cases. llvm-svn: 157353
OpenPOWER on IntegriCloud