From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] MI notification on record started and stopped
Date: Thu, 13 Sep 2012 17:33:00 -0000 [thread overview]
Message-ID: <83r4q5vne6.fsf@gnu.org> (raw)
In-Reply-To: <50519FC6.3090704@codesourcery.com>
> Date: Thu, 13 Sep 2012 16:56:38 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
>
> On 09/13/2012 01:51 AM, Eli Zaretskii wrote:
> >> +The process record is either started or stoped in process @var{id}.
> >> >+The @var{id} field contains the @value{GDBN} identifier of process.
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > "contains the @value{GDBN} process ID."
> >
> > By the way: why is it useful to have the GDB PID part of this
> > notification? Can you have more than one GDB process at a time that
> > all communicate on the same wire?
> >
> > Or did you mean the inferior PID?
>
> I meant the inferior PID. Originally I wrote "inferior ID" in doc, but
> I found "inferior ID" is never used in gdb.texinfo. Looks
> "@value{GDBN} identifier of the" is used. In this version, I change it
> to:
>
> "contains the @value{GDBN} identifier of the process",
>
> because this pattern is used some times in doc. Is it OK?
Sorry, I don't understand: is that parameter the OS PID of the
inferior, or is that the inferior number displayed in the first column
of the "info inferiors" output?
next prev parent reply other threads:[~2012-09-13 17:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 7:16 [PATCH 0/2] Two MI notifications on TSV and process record Yao Qi
2012-09-12 7:16 ` [PATCH 1/2] MI notification on tsv created and deleted Yao Qi
2012-09-12 17:48 ` Eli Zaretskii
2012-09-18 12:19 ` [committed]: " Yao Qi
2012-09-13 20:17 ` Tom Tromey
2012-09-12 7:16 ` [PATCH 2/2] MI notification on record started and stopped Yao Qi
2012-09-12 17:52 ` Eli Zaretskii
2012-09-13 8:57 ` Yao Qi
2012-09-13 17:33 ` Eli Zaretskii [this message]
2012-09-14 2:54 ` Yao Qi
2012-09-14 9:49 ` Eli Zaretskii
2012-09-14 11:45 ` Yao Qi
2012-09-14 12:09 ` Pedro Alves
2012-09-14 13:14 ` Yao Qi
2012-09-14 14:13 ` Pedro Alves
2012-09-21 1:47 ` [committed]: " Yao Qi
2012-09-21 6:58 ` Regression for gdb.mi/mi-reverse.exp [Re: [committed]: [PATCH 2/2] MI notification on record started and stopped] Jan Kratochvil
2012-09-21 7:26 ` Yao Qi
2012-09-14 13:30 ` [PATCH 2/2] MI notification on record started and stopped Eli Zaretskii
2012-09-12 18:07 ` Tom Tromey
2012-09-12 19:04 ` Pedro Alves
2012-09-12 19:01 ` Pedro Alves
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=83r4q5vne6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@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