Yes somehow my system thought I had no commit message after saving from my editor.
This patch makes sure that any options passed to lldb command line driver, like the "-s FILE", "-S FILE", "-o CMD", "-O CMD" and the target you create directly from the LLDB command line args is saved into a file and executed in the command interpreter just as if it was typed in. Previous so this fix any commands specified were run using SBCommandInterpreter::HandleCommand(...) and then the results were printed in a way that wasn't consistent as if they were typed in. It also allows commands to be interrupted so if you do: % lldb -n my_process_name --waitfor You can interrupt it with ^C. What this does is saves all commands to a temp text file, runs the command interpreter with that text file by setting the STDIN of the debugger to be the temp text file, then it runs until EOF and exits, then we set the STDIN to the actual standard input, and it runs the command interpreter again. Greg > On Jul 30, 2014, at 10:59 AM, Reid Kleckner <[email protected]> wrote: > > On Wed, Jul 30, 2014 at 10:38 AM, Greg Clayton <[email protected]> wrote: > Author: gclayton > Date: Wed Jul 30 12:38:47 2014 > New Revision: 214319 > > URL: http://llvm.org/viewvc/llvm-project?rev=214319&view=rev > Log: (empty) > > Looks like the commit message got lost along the way. _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
