From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13880 invoked by alias); 31 Mar 2003 23:06:04 -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 13871 invoked from network); 31 Mar 2003 23:06:02 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (209.53.16.215) by sources.redhat.com with SMTP; 31 Mar 2003 23:06:02 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 1676DD34B8; Mon, 31 Mar 2003 15:05:56 -0800 (PST) Date: Mon, 31 Mar 2003 23:06:00 -0000 From: Joel Brobecker To: gdb-patches@sources.redhat.com Subject: [RFA/doco] Adjust the normal_stop observer documentation Message-ID: <20030331230556.GG916@gnat.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2B/JsCI69OhZNC5r" Content-Disposition: inline User-Agent: Mutt/1.4i X-SW-Source: 2003-03/txt/msg00621.txt.bz2 --2B/JsCI69OhZNC5r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 522 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). 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. Ok to apply? Thanks, -- Joel --2B/JsCI69OhZNC5r Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="observer.texi.diff" Content-length: 1958 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 31 Mar 2003 22:56:30 -0000 *************** *** 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. *************** *** 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: --2B/JsCI69OhZNC5r--