From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28675 invoked by alias); 1 Apr 2003 01:00:12 -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 28575 invoked from network); 1 Apr 2003 00:59:54 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (209.53.16.215) by sources.redhat.com with SMTP; 1 Apr 2003 00:59:54 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id A86ECD34B8; Mon, 31 Mar 2003 16:59:46 -0800 (PST) Date: Tue, 01 Apr 2003 01:00:00 -0000 From: Joel Brobecker To: gdb-patches@sources.redhat.com Subject: Re: [RFA/doco] Adjust the normal_stop observer documentation Message-ID: <20030401005946.GD921@gnat.com> References: <20030331230556.GG916@gnat.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <20030331230556.GG916@gnat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-04/txt/msg00002.txt.bz2 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 897 > 2003-03-31 J. Brobecker > > * observer.texi (GDB Observers): Adjust the documentation for the > normal_stop notification to better describe reality. Fix a minor > typo. Second attempt, including Daniel's suggestion to document when the breakpoint conditions and commands are evaluated relative to the moment the normal_stop event is emitted. 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 couple of minor nits. New changelog: 2003-03-31 J. Brobecker * observer.texi (GDB Observers): Adjust the documentation for the normal_stop notification to better describe reality. Fix a couple of minor typos. -- Joel --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="observer.texi.diff" Content-length: 2976 Index: observer.texi =================================================================== RCS file: /cvs/src/src/gdb/doc/observer.texi,v retrieving revision 1.1 diff -c -3 -r1.1 observer.texi *** observer.texi 18 Mar 2003 17:44:23 -0000 1.1 --- observer.texi 1 Apr 2003 00:53:00 -0000 *************** *** 12,18 **** One subject can have several observers. @file{observer.c} implements an internal generic low-level event ! notification mechanism. This generic event notification mechansim is then re-used to implement the exported high-level notification management routines for all possible notifications. --- 12,18 ---- One subject can have several observers. @file{observer.c} implements an internal generic low-level event ! notification mechanism. This generic event notification mechanism is then re-used to implement the exported high-level notification management routines for all possible notifications. *************** *** 27,33 **** callback is detached. This is not a problem so far, as this contextual data is only used internally to hold a function pointer. Later on, if a certain observer needs to provide support for user-level contextual ! data, then the generic notification mechanism will need need to be enhanced to allow the observer to provide a routine to deallocate the data when attaching the callback. --- 27,33 ---- callback is detached. This is not a problem so far, as this contextual data is only used internally to hold a function pointer. Later on, if a certain observer needs to provide support for user-level contextual ! data, then the generic notification mechanism will need to be enhanced to allow the observer to provide a routine to deallocate the data when attaching the callback. *************** *** 39,48 **** @cindex @code{normal_stop} observer @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: --- 39,54 ---- @cindex @code{normal_stop} observer @cindex notification about inferior execution stop ! @value{GDBN} notifies 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. ! ! Note that the @code{normal_stop} notification is not emitted when ! the execution stops due to a breakpoint, and this breakpoint has ! a condition that is not met. If the breakpoint has any associated ! commands list, the commands are executed after the notification ! is emitted. The following interface is available to manage @code{normal_stop} observers: --azLHFNyN32YCQGCU--