From: Keith Seitz <keiths@redhat.com>
To: <thomson@ca.ibm.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: [MI] Synchronous event notification
Date: Fri, 24 May 2002 15:31:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0205241527560.29198-100000@makita.cygnus.com> (raw)
In-Reply-To: <OF90A649BA.6CAC8AFF-ON85256BC2.0062B9AF@torolab.ibm.com>
On Fri, 24 May 2002 thomson@ca.ibm.com wrote:
> result ==>
> stuff ( "," event ) *
> event ==>
> "MI_HOOK_RESULT=[HOOK_TYPE=" event-name [ event-data ] "]"
Yes, that's right. My boo-boo.
> That means there are several
> ways a UI is notified of breakpoint creation
>
> after -break-insert, you get
> ^done,bkpt=[number="1",type="breakpoint", ...]
>
> after -interpreter-exec console "break ...", or
> using -interpreter-exec to run a user defined command
> or script that creates breakpoints, you are proposing
> ^done,event=[name="breakpoint_create", ...]
>
> from a breakpoint command list (e.g. enable bkpt 2
> after bkpt 1 is hit 100 times) ...
Right. See my follow-up message to Andrew. I would like to reduce this all
to async event notification. (Well, initially we'll probably just leave
this specific thing alone. MI parsers could just ignore it.)
> As consumers, we would prefer to have one notification
> that is reliable and consistent.
Me, too. :-)
> Are you also looking at the other, non-event hooks
> Apple introduced?
I will be eventually. Right now it's back to basics. All the hooks will be
turned into events (as far as possible).
Keith
next prev parent reply other threads:[~2002-05-24 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 14:52 thomson
2002-05-24 15:31 ` Keith Seitz [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=Pine.GSO.4.33.0205241527560.29198-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=thomson@ca.ibm.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