Re: MI3 and async notifications

Jan Vrany
2019-06-20T20:46:15Z

On Thu, 2019-06-20 at 11:31 -0400, Simon Marchi wrote:
>
> Ok, then I understand how ugly it is to try to track the commands and their responses. I would tend to
> say that it falls in the category "you're not using it the way it was intended to":

Fair enough :-)

>
> I am still unsure about emitting events unconditionally. For example: some frontends want to
> insert "internal" breakpoints, which are breakpoints that are not going to be directly shown to
> users. They send a -break-insert and decide that the breakpoint which results from this won't be
> propagated to the UI. But breakpoint async events are propagated to the UI (presumably because
> they originate from the user creating a breakpoint in the CLI). If GDB now emits an event for
> the -break-insert breakpoint, the frontend can't know right away which future =breakpoint-created
> event it should ignore. Again, it would need to buffer all =breakpoint-created events until it
> gets the ^done, then let pass through all events except the one that matches the created breakpoint.
>
Yeah, that would be tricky.

Okay, it looks I lost this case. That's fine.

Thanks!

Jan