From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: Simon Marchi <simark@simark.ca>,
"gdb@sourceware.org" <gdb@sourceware.org>
Cc: "Joel Brobecker" <brobecker@adacore.com>,
"Tom Tromey" <tom@tromey.com>,
"André Pönitz" <apoenitz@t-online.de>,
"Jonah Graham" <jonah@kichwacoders.com>
Subject: Re: MI3 and async notifications
Date: Thu, 20 Jun 2019 20:46:00 -0000 [thread overview]
Message-ID: <d4ed73ee5cea2c463628570e15fe064faa1355b9.camel@fit.cvut.cz> (raw)
In-Reply-To: <5687f162-d938-7eff-55ba-cf72d9d91e58@simark.ca>
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
next prev parent reply other threads:[~2019-06-20 20:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 21:19 Jan Vrany
2019-06-10 23:23 ` Jonah Graham
2019-06-11 8:50 ` Jan Vrany
2019-06-11 13:37 ` Jonah Graham
2019-07-05 20:00 ` Pedro Alves
2019-07-05 21:58 ` Jonah Graham
2019-06-15 14:34 ` Tom Tromey
2019-06-17 10:53 ` Jan Vrany
2019-06-17 12:11 ` Jonah Graham
2019-06-17 12:14 ` Joel Brobecker
2019-06-17 12:26 ` Jonah Graham
2019-06-17 12:56 ` Joel Brobecker
2019-06-17 13:12 ` Jonah Graham
2019-06-17 13:12 ` Jan Vrany
2019-06-17 13:23 ` Jonah Graham
2019-06-17 20:45 ` Joel Brobecker
2019-06-17 20:58 ` Jan Vrany
2019-06-17 21:50 ` Jonah Graham
2019-06-17 19:52 ` André Pönitz
2019-06-18 3:14 ` Simon Marchi
2019-06-18 20:38 ` Jan Vrany
2019-06-19 15:29 ` Simon Marchi
2019-06-19 20:58 ` Jan Vrany
2019-06-20 15:31 ` Simon Marchi
2019-06-20 20:46 ` Jan Vrany [this message]
2019-07-05 19:35 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4ed73ee5cea2c463628570e15fe064faa1355b9.camel@fit.cvut.cz \
--to=jan.vrany@fit.cvut.cz \
--cc=apoenitz@t-online.de \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jonah@kichwacoders.com \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).