[Lldb-commits] [PATCH] Fix handling of hijacked events in synchronous mode

[jingham at apple.com]

BTW, if you are in async mode and you want to know if some command caused the process to run, you can just check the Process StopID (SBProcess::GetStopID().)  You want the default value for include_expression_stops, since you don't want to say "stopped" if somebody ran a function call.  Anyway, if the StopID has gone up, the target was run, and (in sync mode) has stopped again...

Jim

> On May 8, 2015, at 10:48 AM, Jim Ingham <jingham at apple.com> wrote:
> 
> Why do you ever need to run the MI in sync mode?  If you want to get events when the process changes state, use async mode, that's what it is for.  Changing the nature of "sync" so it starts producing events is also the wrong solution.
> 
> Jim
> 
> 
> http://reviews.llvm.org/D9371
> 
> EMAIL PREFERENCES
>  http://reviews.llvm.org/settings/panel/emailpreferences/
> 
>