From: Jonah Graham <jonah@kichwacoders.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Vrany <jan.vrany@fit.cvut.cz>, Tom Tromey <tom@tromey.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: MI3 and async notifications
Date: Mon, 17 Jun 2019 13:12:00 -0000 [thread overview]
Message-ID: <CAPmGMvg+oKYBkrOezbx1BimHew6uL6qyy=CNrXf7++FhRkis0Q@mail.gmail.com> (raw)
In-Reply-To: <20190617125638.GA6859@adacore.com>
On Mon, 17 Jun 2019 at 08:56, Joel Brobecker <brobecker@adacore.com> wrote:
> The part I don't understand is why it matters to sync the two.
>
For example, to allow program to update the UI element that represents a
breakpoint. In CDT when a breakpoint is inserted in the UI and fails to be
installed or is only pending the UI element is updated to display that
fact. CDT maintains a map of UI elements to GDB instances+breakpoint
numbers. That connection (UI element to breakpoint number) is made as
result of the response to -break-insert.
The UI elements are breakpoints in a table, or in the margin of an editor.
Does that make sense?
next prev parent reply other threads:[~2019-06-17 13:12 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 [this message]
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
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='CAPmGMvg+oKYBkrOezbx1BimHew6uL6qyy=CNrXf7++FhRkis0Q@mail.gmail.com' \
--to=jonah@kichwacoders.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
--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).