Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Mon, 17 May 2004 20:10:00 -0000	[thread overview]
Message-ID: <40A91C36.7000900@gnu.org> (raw)
In-Reply-To: <409A8C2A.2010605@gnu.org>

Eli,

How does the doco here look? (everone appears ok on this part of the 
mechanism).

Andrew
2004-05-10  Andrew Cagney  <cagney@redhat.com>

	* observer.texi (GDB Observers): Document "inferior_created".

Index: doc/observer.texi
===================================================================
RCS file: /cvs/src/src/gdb/doc/observer.texi,v
retrieving revision 1.6
diff -p -u -r1.6 observer.texi
--- doc/observer.texi	7 May 2004 22:51:55 -0000	1.6
+++ doc/observer.texi	17 May 2004 20:05:44 -0000
@@ -82,3 +82,11 @@ The inferior has stopped for real.
 @deftypefun void target_changed (struct target_ops *@var{target})
 The target's register contents have changed.
 @end deftypefun
+
+@deftypefun void inferior_created (struct target_ops *@var{objfile}, int @var{from_tty})
+@var{GDBN} has just created to a new inferior.  For @samp{run}, it is
+called while the inferior is still stopped at the entry-point
+instruction.  For @samp{attach} and @samp{core}, it is called
+immediatly after opening the inferior (and before any information on
+the inferior has been printed).
+@end deftypefun
From kevinb@redhat.com Mon May 17 20:19:00 2004
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Mon, 17 May 2004 20:19:00 -0000
Message-id: <20040517131914.332fa347@saguaro>
References: <409A8C2A.2010605@gnu.org> <40A91C36.7000900@gnu.org>
X-SW-Source: 2004-05/msg00506.html
Content-length: 530

On Mon, 17 May 2004 16:10:30 -0400
Andrew Cagney <cagney@gnu.org> wrote:

> +@deftypefun void inferior_created (struct target_ops *@var{objfile}, int @var{from_tty})
> +@var{GDBN} has just created to a new inferior.  For @samp{run}, it is
> +called while the inferior is still stopped at the entry-point
> +instruction.  For @samp{attach} and @samp{core}, it is called
> +immediatly after opening the inferior (and before any information on
> +the inferior has been printed).
> +@end deftypefun

s/immediatly/immediately/

Kevin


  parent reply	other threads:[~2004-05-17 20:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  1:19 Andrew Cagney
2004-05-07  0:48 ` Roland McGrath
2004-05-07  1:31   ` Daniel Jacobowitz
2004-05-10 21:39     ` Andrew Cagney
2004-05-07  1:19 ` Andrew Cagney
2004-05-07  1:25   ` Daniel Jacobowitz
2004-05-10 21:27     ` Andrew Cagney
2004-05-11  5:15       ` Mark Kettenis
2004-05-11 14:49         ` Andrew Cagney
2004-05-11 14:53         ` Daniel Jacobowitz
     [not found]           ` <40A0FFB1.8030407@gnu.org>
2004-05-11 17:26             ` Daniel Jacobowitz
2004-05-12  0:28               ` Andrew Cagney
2004-05-15 20:58                 ` Mark Kettenis
2004-05-17 17:14                   ` Revamp sniffer; Was: " Andrew Cagney
2004-05-25 22:55                     ` Andrew Cagney
2004-06-11 17:32                       ` Andrew Cagney
2004-06-15 20:17                         ` Andrew Cagney
2004-06-16 23:07                           ` Roland McGrath
2004-06-24 18:10                             ` Andrew Cagney
2004-06-24 20:59                               ` Roland McGrath
2004-06-24 21:20                                 ` Mark Kettenis
2004-05-17 20:10 ` Andrew Cagney [this message]
     [not found]   ` <20040517131914.332fa347@saguaro>
2004-05-18  5:59     ` Eli Zaretskii
2004-05-18 20:09       ` Andrew Cagney
2004-05-19  5:50         ` Eli Zaretskii
2004-05-19 14:47           ` Andrew Cagney
2004-05-19 21:10             ` Eli Zaretskii
2004-05-20  5:33               ` 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=40A91C36.7000900@gnu.org \
    --to=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --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