From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Multiexec MI
Date: Sat, 20 Feb 2010 13:39:00 -0000 [thread overview]
Message-ID: <83mxz4vxep.fsf@gnu.org> (raw)
In-Reply-To: <201002201354.56081.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 20 Feb 2010 13:54:55 +0300
> Cc: gdb-patches@sourceware.org
>
> > The @var{thread-group} field, if present, specifies the id of the
> > thread group in whose context the library was loaded.
> >
> > Does this express what you meant?
>
> Oh, it does. Thanks.
>
> > > > > +Identifier of the thread group. This field is always present. The
> > > > > +identifier is an opaque string, and is not necessary an integer.
> > > > ^^^^^^^^^
> > > > "necessarily"
> > > >
> > > > Also, "is an opaque string, and is not necessarily an integer" sounds
> > > > strange: if it's a string, how can it be an integer? Do you mean to
> > > > say that the string includes non-digit characters?
> > >
> > > How about: "The identifier is an opaque string; frontends should not
> > > try to convert it to integer".
> >
> > I suggest a slight variation:
> >
> > The identifier is an opaque string; frontends should not try to
> > convert it to an integer, even though it might look like one.
>
> I've used your wording. Revised patch attached.
It's okay, but please fix this small typo when you commit:
> --- a/gdb/doc/observer.texi
> +++ b/gdb/doc/observer.texi
> @@ -199,13 +199,23 @@ The thread's ptid has changed. The @var{old_ptid} parameter specifies
> the old value, and @var{new_ptid} specifies the new value.
> @end deftypefun
>
> -@deftypefun void inferior_appeared (int @var{pid})
> -@value{GDBN} has attached to a new inferior identified by @var{pid}.
> +@deftypefun void inferior_added (struct inferior *@var{inf})
> +The inferior @var{inf} has been added to the list of inferior. At
^^^^^^^^
This should be "inferiors".
Thanks.
next prev parent reply other threads:[~2010-02-20 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 20:29 Vladimir Prus
2010-01-13 21:04 ` Eli Zaretskii
2010-02-19 19:54 ` Vladimir Prus
2010-02-19 21:06 ` Eli Zaretskii
2010-02-20 10:55 ` Vladimir Prus
2010-02-20 13:39 ` Eli Zaretskii [this message]
2010-02-08 19:20 ` Pedro Alves
2010-02-08 19:28 ` Pedro Alves
2010-02-20 11:59 ` Vladimir Prus
2010-02-19 20:16 ` Vladimir Prus
2010-02-22 12:16 ` Pedro Alves
2010-02-24 7:53 ` Vladimir Prus
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=83mxz4vxep.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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