This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/2] MI notification on record started and stopped
> 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?