From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: kevinb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Wed, 19 May 2004 05:50:00 -0000 [thread overview]
Message-ID: <ulljo29vh.fsf@gnu.org> (raw)
In-Reply-To: <40AA6D88.50003@gnu.org>
> Date: Tue, 18 May 2004 16:09:44 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> 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
Yes, much better.
Of course, following RMS's advice to avoid passive, "@value{GDBN}
calls this observer..." instead of "this observer is called..." would
be even better ;-)
> ... but the ``connecting to the inferior'' near the end is struggling a bit.
The only thing that bothers me is whether ``connecting'' is something
that the reader will instantly understand. Other than that, I don't
see any problems here.
next prev parent reply other threads:[~2004-05-19 5:50 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
[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 [this message]
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=ulljo29vh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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