OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* observer.texi (GDB Observers): Adjust the documentation for the 

normal_stop notification to better describe reality. Fix a couple
        of minor typos.
This commit is contained in:
Joel Brobecker 2003-04-03 15:14:48 +00:00
parent 29b058f1b4
commit 6be67e674a
2 changed files with 18 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/doc/ChangeLog
View File

@ -1,3 +1,9 @@
2003-04-02 J. Brobecker <brobecker@gnat.com>
* observer.texi (GDB Observers): Adjust the documentation for the
normal_stop notification to better describe reality. Fix a couple
of minor typos.
2003-04-02 Bob Rossi <bob_rossi@cox.net>
* gdb.texinfo (GDB/MI Program Control): Add

18
gdb/doc/observer.texi
View File

@ -12,7 +12,7 @@ notifications, the observer attaches a callback to the subject.
One subject can have several observers.
@file{observer.c} implements an internal generic low-level event
notification mechanism. This generic event notification mechansim is
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,7 +27,7 @@ as it lacks a mechanism that would deallocate this data when the
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
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,10 +39,16 @@ or detach routines during a notification.
@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.
@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: