From: Andrew Cagney <ac131313@cygnus.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [MI] Synchronous event notification
Date: Sat, 01 Jun 2002 15:25:00 -0000 [thread overview]
Message-ID: <3CF949CC.5080108@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0205241520470.29198-100000@makita.cygnus.com>
> UIs prefer to respond to events when something happens. In the later case
> above, we've asked gdb to install a breakpoint at main, but the UI won't
> actually do anything (like update breakpoint markers or breakpoint
> windows) UNTILL it gets the event from gdb.
>
> So, if we need to vote, I vote that we output aync events all the time.
> (Of course, this would mean we really need to get target output nailed
> for the natives, but that's another battle.)
I don't think a vote is needed - it matches the original MI intent. All
events were to be considered considered async.
Andrew
next prev parent reply other threads:[~2002-06-01 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 11:23 Keith Seitz
2002-05-24 13:41 ` Andrew Cagney
2002-05-24 15:26 ` Keith Seitz
2002-06-01 15:25 ` Andrew Cagney [this message]
2002-05-24 14:52 thomson
2002-05-24 15:31 ` Keith Seitz
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=3CF949CC.5080108@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=keiths@redhat.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