This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [MI] Synchronous event notification
- From: Keith Seitz <keiths at redhat dot com>
- To: <thomson at ca dot ibm dot com>
- Cc: <gdb at sources dot redhat dot com>
- Date: Fri, 24 May 2002 15:31:17 -0700 (PDT)
- Subject: Re: [MI] Synchronous event notification
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