From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28159 invoked by alias); 13 Aug 2005 01:11:34 -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 27220 invoked by uid 22791); 13 Aug 2005 01:10:25 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 13 Aug 2005 01:10:25 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1E3kXX-0001Bo-MZ for gdb-patches@sources.redhat.com; Fri, 12 Aug 2005 21:10:23 -0400 Date: Sat, 13 Aug 2005 01:15:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Subject: Re: RFC: MI output during program execution Message-ID: <20050813011023.GA4557@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com References: <20050810004128.GA4264@nevyn.them.org> <20050810004826.GD3557@white> <2040BEEA-4200-4118-91EB-D093ED4D37A1@apple.com> <20050812012810.GA10011@white> <20050812114929.GB10917@white> <20050812203052.GA11539@white> <20050812204541.GA30801@nevyn.them.org> <20050813004940.GB11892@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050813004940.GB11892@white> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-08/txt/msg00150.txt.bz2 On Fri, Aug 12, 2005 at 08:49:40PM -0400, Bob Rossi wrote: > I believe I understand now. I think you are saying that at certain > interesting points in GDB (when it realizes breakpoints have changed, > or the inferior changes state), then an event is generated, and the > MI (still inside GDB), is the consumer of that event. Is this correct? > > With this in mind, the way MI gets the data (callbacks, Observer > pattern, hooks/events) is what is important, and *not* the way the MI > jet's this data to the FE. Is this correct? All correct. The MI pipes the information to the FE, well, via MI... -- Daniel Jacobowitz CodeSourcery, LLC