From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20319 invoked by alias); 24 May 2002 22:31:39 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20262 invoked from network); 24 May 2002 22:31:32 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 24 May 2002 22:31:32 -0000 Received: from makita.cygnus.com (makita.sfbay.redhat.com [192.168.30.83]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id PAA16593; Fri, 24 May 2002 15:31:27 -0700 (PDT) Received: from localhost (keiths@localhost) by makita.cygnus.com (8.8.8+Sun/8.6.4) with ESMTP id PAA19796; Fri, 24 May 2002 15:31:17 -0700 (PDT) X-Authentication-Warning: makita.cygnus.com: keiths owned process doing -bs Date: Fri, 24 May 2002 15:31:00 -0000 From: Keith Seitz X-X-Sender: To: cc: Subject: Re: [MI] Synchronous event notification In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-05/txt/msg00275.txt.bz2 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