summaryrefslogtreecommitdiffstats
path: root/lldb/examples/python/cmdtemplate.py
Commit message (Collapse)AuthorAgeFilesLines
* Tweaks to the Python reference and example command to use the preferred ↵Enrico Granata2013-07-111-5/+5
| | | | | | print style and the (finally available :-) SetError API llvm-svn: 186122
* Providing a more interesting command template for LLDBEnrico Granata2013-05-091-25/+41
| | | | | | This one actually exploits the SB API to obtain information about your inferior process llvm-svn: 181500
* Being explicit about how ignoring optparse's exceptions is not a best principleEnrico Granata2013-02-251-0/+2
| | | | llvm-svn: 176059
* Mark the command as failed if parsing fails.Jim Ingham2013-02-211-0/+1
| | | | llvm-svn: 175776
* Modified the command template to include best practices.Greg Clayton2012-09-131-17/+24
| | | | llvm-svn: 163773
* Added a 'gdbremote' python module that adds two commands: start_gdb_log and ↵Greg Clayton2012-01-261-4/+4
| | | | | | | | | | | | | | | end_gdb_log. When this is imported into your lldb using the "command script import /path/to/gdbremote.py" these new commands are available within LLDB. 'start_gdb_log' will enable logging with timestamps for GDB remote packets, and 'stop_gdb_log' will then dump the details and also a lot of packet timing data. This allows us to accurately track what packets are taking up the most time when debugging (when using the ProcessGDBRemote debugging plug-in). Also udpated the comments at the top of the cmdtemplate.py to show how to correctly import the module from within LLDB. llvm-svn: 149030
* Proof-reading the python docs.Jim Ingham2012-01-241-5/+6
| | | | llvm-svn: 148768
* Added a python FAQ page with detailed examples of how to add python functionsGreg Clayton2012-01-221-0/+49
to breakpoints, creating new LLDB commands using python modules and also how to run scripts from the command line. llvm-svn: 148650
OpenPOWER on IntegriCloud