From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11904 invoked by alias); 13 Sep 2012 17:33:12 -0000 Received: (qmail 11855 invoked by uid 22791); 13 Sep 2012 17:33:10 -0000 X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Sep 2012 17:32:53 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MAA00100U0NFJ00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Thu, 13 Sep 2012 20:32:52 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MAA0009JU2ROMD0@a-mtaout22.012.net.il>; Thu, 13 Sep 2012 20:32:52 +0300 (IDT) Date: Thu, 13 Sep 2012 17:33:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 2/2] MI notification on record started and stopped In-reply-to: <50519FC6.3090704@codesourcery.com> To: Yao Qi Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83r4q5vne6.fsf@gnu.org> References: <1347434118-10931-1-git-send-email-yao@codesourcery.com> <1347434118-10931-3-git-send-email-yao@codesourcery.com> <838vcfw2my.fsf@gnu.org> <50519FC6.3090704@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00250.txt.bz2 > Date: Thu, 13 Sep 2012 16:56:38 +0800 > From: Yao Qi > CC: > > 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?