From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14454 invoked by alias); 12 Sep 2012 17:52:02 -0000 Received: (qmail 14439 invoked by uid 22791); 12 Sep 2012 17:52:00 -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 mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Sep 2012 17:51:47 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MA90020008O7B00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Wed, 12 Sep 2012 20:51:22 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MA9000Q409MTBO0@a-mtaout20.012.net.il>; Wed, 12 Sep 2012 20:51:22 +0300 (IDT) Date: Wed, 12 Sep 2012 17:52:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 2/2] MI notification on record started and stopped In-reply-to: <1347434118-10931-3-git-send-email-yao@codesourcery.com> To: Yao Qi Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <838vcfw2my.fsf@gnu.org> References: <1347434118-10931-1-git-send-email-yao@codesourcery.com> <1347434118-10931-3-git-send-email-yao@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/msg00216.txt.bz2 > From: Yao Qi > Date: Wed, 12 Sep 2012 15:15:18 +0800 > > +@item =record-started,id=@var{id} > +@item =record-stopped,id=@var{id} The second line should use "@itemx", otherwise the result will be ugly. > +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? Thanks.