3 Commits

Author	SHA1	Message	Date
Jim Ingham	ffc9f1de34	This adds a "batch mode" to lldb kinda like the gdb batch mode. It will quit the debugger ... after all the commands have been executed except if one of the commands was an execution control command that stopped because of a signal or exception. Also adds a variant of SBCommandInterpreter::HandleCommand that takes an SBExecutionContext. That way you can run an lldb command targeted at a particular target, thread or process w/o having to select same before running the command. Also exposes CommandInterpreter::HandleCommandsFromFile to the SBCommandInterpreter API, since that seemed generally useful. llvm-svn: 219654	2014-10-14 01:20:07 +00:00
Enrico Granata	06be059ad9	Allow Python commands to optionally take an SBExecutionContext argument in case they need to handle 'where they want to act' separately from the notion of 'currently-selected entity' that is associated to the debugger. Do this in an (hopefully) non-breaking way by running an argcount check before passing in the new argument. Update the test case to also check for this new feature. www update to follow ... llvm-svn: 218834	2014-10-01 21:47:29 +00:00
Enrico Granata	e85e84a769	Add a new SBExecutionContext class that wraps an ExecutionContextRef. This class is a convenient way at the API level to package a target,process,thread and frame all together - or just a subset of those ... llvm-svn: 218808	2014-10-01 20:43:45 +00:00