From: Daniel Jacobowitz <drow@mvista.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/doco] Add documentation for observer.[hc] (gdbint.texinfo)
Date: Sun, 09 Mar 2003 15:36:00 -0000 [thread overview]
Message-ID: <20030309153623.GA16348@nevyn.them.org> (raw)
In-Reply-To: <20030309065155.GB966@gnat.com>
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
next prev parent reply other threads:[~2003-03-09 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 6:51 Joel Brobecker
2003-03-09 15:36 ` Daniel Jacobowitz [this message]
2003-03-10 14:41 ` Andrew Cagney
2003-03-10 18:46 ` Joel Brobecker
2003-03-09 16:10 ` Eli Zaretskii
2003-03-10 19:01 ` Joel Brobecker
2003-03-10 20:04 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030309153623.GA16348@nevyn.them.org \
--to=drow@mvista.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox