From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27225 invoked by alias); 14 Sep 2012 13:14:30 -0000 Received: (qmail 26876 invoked by uid 22791); 14 Sep 2012 13:14:27 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 14 Sep 2012 13:14:13 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1TCVil-0002JK-M3 from Yao_Qi@mentor.com ; Fri, 14 Sep 2012 06:14:11 -0700 Received: from SVR-ORW-FEM-02.mgc.mentorg.com ([147.34.96.206]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 14 Sep 2012 06:14:11 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-02.mgc.mentorg.com (147.34.96.168) with Microsoft SMTP Server id 14.1.289.1; Fri, 14 Sep 2012 06:14:10 -0700 Message-ID: <50532D6D.5060400@codesourcery.com> Date: Fri, 14 Sep 2012 13:14:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Pedro Alves CC: Eli Zaretskii , Subject: Re: [PATCH 2/2] MI notification on record started and stopped 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> <83r4q5vne6.fsf@gnu.org> <50529C21.5020909@codesourcery.com> <83boh9ue6b.fsf@gnu.org> <505318AD.50603@codesourcery.com> <50531E46.4090708@redhat.com> In-Reply-To: <50531E46.4090708@redhat.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit 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/msg00283.txt.bz2 On 09/14/2012 08:08 PM, Pedro Alves wrote: > On 09/14/2012 12:44 PM, Yao Qi wrote: >> On 09/14/2012 05:49 PM, Eli Zaretskii wrote: >>>> The notification is like '=record-started,thread-group="i1"'. >>> ?? If this is a thread-group, why does i1 identify a_process_? Don't >>> you mean "thread group"? >> >> As matter of fact, this is an inferior, but in MI notification, we call "inferior" as "thread group", IIUC. So i1 identify an inferior. Your suggestion "the number assigned by @value{GDBN} to the inferior" is good to me. > > In these cases, I'd just go and copy what is written in other similar > cases already in the manual. Should make the end overall result a bit more > consistent. For example, borrowing from the "-add-inferior" command's text, > you'd get something like: > > "The notification has a single field, @samp{thread-group}, whose value is the > identifier of the thread group corresponding to the affected inferior." > How about this? The process record was either started or stopped in thread group @var{id}. The @var{id} is the identifier of the thread group corresponding to the affected inferior. -- Yao