From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20552 invoked by alias); 31 Mar 2003 23:17:01 -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 20538 invoked from network); 31 Mar 2003 23:17:01 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 31 Mar 2003 23:17:01 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 1908WR-00057B-00 for ; Mon, 31 Mar 2003 17:16:59 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 1908WN-00025E-00 for ; Mon, 31 Mar 2003 18:16:55 -0500 Date: Mon, 31 Mar 2003 23:17:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Subject: Re: [RFA/doco] Adjust the normal_stop observer documentation Message-ID: <20030331231655.GA7931@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com References: <20030331230556.GG916@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030331230556.GG916@gnat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-03/txt/msg00624.txt.bz2 On Mon, Mar 31, 2003 at 03:05:56PM -0800, Joel Brobecker wrote: > Hello, > > The normal_stop notification has been inserted in a slightly different > location than the location I had in mind. As a consequence, the > description for this notification needed to be slightly adjusted. I took > this opportunity to fix a minor nit (same word repeated twice). > *************** > *** 40,48 **** > @cindex notification about inferior execution stop > > @value{GDBN} will notify all @code{normal_stop} observers when the > ! inferior execution has just stopped, and all the associated internal > ! processing (such as breakpoint commands, annotations, etc) is about to > ! be performed before the @value{GDBN} prompt is returned to the user. > > The following interface is available to manage @code{normal_stop} > observers: > --- 40,48 ---- > @cindex notification about inferior execution stop > > @value{GDBN} will notify all @code{normal_stop} observers when the > ! inferior execution has just stopped, the associated messages and > ! annotations have been printed, and the control is about to be returned > ! to the user. > > The following interface is available to manage @code{normal_stop} > observers: Have user breakpoint commands been executed at this point? How about breakpoint conditions? If so, it suggests that the cache management you wanted for Ada needs to be done at an earlier observation point, perhaps corresponding to each _actual_ stop as opposed to each user visible stop. Otherwise "info tasks" in a breakpoint commands list may behave strangely... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer