From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3080 invoked by alias); 9 Mar 2003 15:36:27 -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 3073 invoked from network); 9 Mar 2003 15:36:27 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 9 Mar 2003 15:36:27 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18s4k1-0007KK-00; Sun, 09 Mar 2003 11:37:41 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18s2qd-0004HM-00; Sun, 09 Mar 2003 10:36:23 -0500 Date: Sun, 09 Mar 2003 15:36:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA/doco] Add documentation for observer.[hc] (gdbint.texinfo) Message-ID: <20030309153623.GA16348@nevyn.them.org> Mail-Followup-To: Joel Brobecker , gdb-patches@sources.redhat.com References: <20030309065155.GB966@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030309065155.GB966@gnat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00204.txt.bz2 On Sat, Mar 08, 2003 at 10:51:55PM -0800, Joel Brobecker wrote: > The following patch adds some light documentation about the new observer > paradigm introduced recently. Thanks. Two things: > *************** > *** 95,100 **** > --- 95,101 ---- > * Hints:: > > * GNU Free Documentation License:: The license for this documentation > + * GDB Observers:: @value{GDBN} Observers currently available > * Index:: > @end menu > Between the GFDL and the Index is probably not a good place for the new chapter. > @section @code{normal_stop} Notifications > > @value{GDBN} will notify all @code{normal_stop} observers when the > inferior execution has just stopped and the @value{GDBN} prompt is > about to be returned to the user. Could you be a little more specific? A lot of things can happen between the application stopping and control returning to the user. For instance: - is it before or after breakpoint commands are run, if we hit a breakpoint? - If we're single-stepping multiple times, does normal_stop get called for each one or only for the last? My guess is that it's closer to the prompt than to the inferior stopping, but I haven't checked. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer