bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	Being explicit about how ignoring optparse's exceptions is not a best principle	Enrico Granata	2013-02-25	1	-0/+2
\| \| \| \|	llvm-svn: 176059
*	Mark the command as failed if parsing fails.	Jim Ingham	2013-02-21	1	-0/+1
\| \| \| \|	llvm-svn: 175776
*	Modified the command template to include best practices.	Greg Clayton	2012-09-13	1	-17/+24
\| \| \| \|	llvm-svn: 163773
*	Added a 'gdbremote' python module that adds two commands: start_gdb_log and ↵	Greg Clayton	2012-01-26	1	-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 Ingham	2012-01-24	1	-5/+6
\| \| \| \|	llvm-svn: 148768
*	Added a python FAQ page with detailed examples of how to add python functions	Greg Clayton	2012-01-22	1	-0/+49
	to breakpoints, creating new LLDB commands using python modules and also how to run scripts from the command line. llvm-svn: 148650