From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Tue, 18 May 2004 20:09:00 -0000
Message-id: <40AA6D88.50003@gnu.org>
References: <409A8C2A.2010605@gnu.org> <40A91C36.7000900@gnu.org> <20040517131914.332fa347@saguaro> <1438-Tue18May2004085728+0300-eliz@gnu.org>
X-SW-Source: 2004-05/msg00536.html

Oops, missed the original message.

Andrew, in addition to the typo caught by Kevin, please correct the
wording some more, viz.:
 - "@var{GDBN}" should be "@value{GDBN}".

 - "has just created to a new inferior" is unclear and incorrect
   English.  Sounds like some word is missing or should be deleted.
 - The "it" in "For @samp{run}", it is called ..." is not very clear;
   I think "For @samp{run}, this observer is called ..." is better.
 - "after opening the inferior" is possibly inaccurate: GDB doesn't
   really ``open'' the inferior, right?
I think this is better ...

@deftypefun void inferior_created (struct target_ops *@var{objfile}, int 
@var{from_tty})
@value{GDBN} has just connected to an inferior.  For @samp{run}, this
observer is called while the inferior is still stopped at the
entry-point instruction.  For @samp{attach} and @samp{core}, this
observer is called immediately after connecting to the inferior, and
before any information on the inferior has been printed).
@end deftypefun

... but the ``connecting to the inferior'' near the end is struggling a bit.

Andrew