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

[jingham at apple.com]

Tell me again what problem you are trying to solve?  In synchronous mode, you always know that when a command that runs the target returns either you stopped, or the program exited.  I don't see why you need an event for that.

Jim


> On May 8, 2015, at 9:13 AM, Ilia K <ki.stfu at gmail.com> wrote:
> 
> In http://reviews.llvm.org/D9371#169068, @jingham wrote:
> 
>> That seems like something you should fix on the MI side.  The point of synchronous execution is that you don't have to worry about the events.  Now you are introducing an extra event that everybody is going to have to deal with.  That doesn't seem right to me.
> 
> 
> The lldb-mi uses public API entirely (not lldb_private) and I don't think it's possible to print *stopped if that event wasn't generated in the lldb core.
> 
> 
> http://reviews.llvm.org/D9371
> 
> EMAIL PREFERENCES
>  http://reviews.llvm.org/settings/panel/emailpreferences/
> 
>