From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22912 invoked by alias); 10 Apr 2013 02:51:02 -0000 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 Received: (qmail 22901 invoked by uid 89); 10 Apr 2013 02:51:02 -0000 X-Spam-SWARE-Status: No, score=-4.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL autolearn=ham version=3.3.1 Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 10 Apr 2013 02:50:56 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1UPl7e-0002u5-OF from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Tue, 09 Apr 2013 19:50:54 -0700 Received: from SVR-ORW-FEM-03.mgc.mentorg.com ([147.34.97.39]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 9 Apr 2013 19:50:54 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-03.mgc.mentorg.com (147.34.97.39) with Microsoft SMTP Server id 14.1.289.1; Tue, 9 Apr 2013 19:50:53 -0700 Message-ID: <5164D38C.8070003@codesourcery.com> Date: Wed, 10 Apr 2013 15:46:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Subject: Re: [PATCH v4 0/5] MI notification on trace started/stopped References: <1358838232-13319-1-git-send-email-yao@codesourcery.com> <1364869917-12803-1-git-send-email-yao@codesourcery.com> In-Reply-To: <1364869917-12803-1-git-send-email-yao@codesourcery.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2013-04/txt/msg00267.txt.bz2 On 04/02/2013 10:31 AM, Yao Qi wrote: > Hi, > The V3.1 can't be applied to CVS trunk clearly, so I resolved these > conflicts and submit them again. > > All doc bits were approved by Eli in V3.1. Regression tested them > on x86_64-linux with {unix, native-gdbserver} x {sync, async}. Is > it OK? Below is the introduction of this series. People who are > familiar with this series, please skip it. > > This patch series adds the MI notifications of 'trace-started' and > 'trace-stopped', which are emitted when > > 1) trace is started or stopped by commands in GDB, > 2) trace is stopped due to some reasons in the remote stub, such as > trace buffer full. > > With these notifications, MI front-end can show the status of trace > up to date. > > Patch 4/5 is to address #1, adding new MI notifications and > notifying observers when the commands are called. #2 needs more work > here, because GDB doesn't know the trace is stopped in the remote > stub. So we need an async remote notification 'Trace' to tell GDB. > That is what patch 3/5 about. Patch 5/5 is to use this async remote > notification 'Trace' and notify trace_changed observer. > > Patch 1/5 and 2/5 are the enhancement to the async remote > notification, which is needed by the rest of patches in this series. > Patch 1/5 adds "annex" for notification, which is helpful 1) to give > more information on each event of notification, 2) to query supported > notifications on "annex" level. Patch 2/5 teaches both GDB and > GDBserver to query supported notifications and annexes in the other > side so that 1) GDBserver doesn't send notifications that GDB doesn't > understand, 2) GDB doesn't have to fetch status from the GDBserver if > a certain notification is supported by GDBserver. Ping. http://sourceware.org/ml/gdb-patches/2013-04/msg00019.html -- Yao (齐尧)