From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5927 invoked by alias); 14 Sep 2012 13:30:31 -0000 Received: (qmail 5919 invoked by uid 22791); 14 Sep 2012 13:30:29 -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; Fri, 14 Sep 2012 13:30:09 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MAC00C00DI66J00@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Fri, 14 Sep 2012 16:30:08 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MAC00BYJDI7FWA0@a-mtaout22.012.net.il>; Fri, 14 Sep 2012 16:30:08 +0300 (IDT) Date: Fri, 14 Sep 2012 13:30:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 2/2] MI notification on record started and stopped In-reply-to: <505318AD.50603@codesourcery.com> To: Yao Qi Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83627gvij4.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> <83r4q5vne6.fsf@gnu.org> <50529C21.5020909@codesourcery.com> <83boh9ue6b.fsf@gnu.org> <505318AD.50603@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/msg00284.txt.bz2 > Date: Fri, 14 Sep 2012 19:44:45 +0800 > From: Yao Qi > CC: > > 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. But all the other places that describe thread-group= fields talk about thread groups, so I think we need to do that here for consistency.