From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19913 invoked by alias); 10 Aug 2005 02:37:53 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18811 invoked by uid 22791); 10 Aug 2005 02:36:03 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 10 Aug 2005 02:36:03 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1E2gRk-0001mV-Kz; Tue, 09 Aug 2005 22:36:00 -0400 Date: Thu, 11 Aug 2005 10:10:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii , Jim Ingham , gdb-patches@sources.redhat.com Subject: Re: RFC: MI output during program execution Message-ID: <20050810023600.GA6697@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Jim Ingham , gdb-patches@sources.redhat.com References: <1123605445.30442.ezmlm@sources.redhat.com> <20050809181311.GB3012@white> <20050809223421.GB3557@white> <20050810004128.GA4264@nevyn.them.org> <20050810004826.GD3557@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050810004826.GD3557@white> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-08/txt/msg00118.txt.bz2 On Tue, Aug 09, 2005 at 08:48:26PM -0400, Bob Rossi wrote: > Here is another odd scenario, Jim, please give some info if you have > experience in this area. > > If you hit a breakpoint, and the observer starts to send you data, does > it > - send all the state data in one async response, in the same response as > the async MI command that says *stopped? > - send all the state data in one async response, in a different response > as the async MI command that says *stopped? > - send all the state data, each in different async response's, in a > different response as the async MI command that says *stopped? > > This may seem unimportant, however I believe it could be marginally > important. For instance, does the front end have to wait for the async > observer response before it can do anything else? I can't speak for what Apple's done, but it seems natural to me like #3. "state data" isn't a great term for this; they're notifications of things, as they happen. So it seems to me that you'd want something like (forgive my syntax, don't take this literally! I don't speak MI at the moment): =breakpoint-changed,[bpnum="1",state="disabled"] =thread-changed,[thread="2"] -- Daniel Jacobowitz CodeSourcery, LLC