From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20269 invoked by alias); 22 Jan 2013 07:05:32 -0000 Received: (qmail 20252 invoked by uid 22791); 22 Jan 2013 07:05:30 -0000 X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=AWL,BAYES_00,FROM_12LTRDOM,KHOP_RCVD_UNTRUST,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; Tue, 22 Jan 2013 07:05:24 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1TxXv9-0000KA-FC from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Mon, 21 Jan 2013 23:05:23 -0800 Received: from SVR-ORW-FEM-03.mgc.mentorg.com ([147.34.97.39]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 21 Jan 2013 23:05:18 -0800 Received: from qiyao.dyndns.org.com (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; Mon, 21 Jan 2013 23:05:17 -0800 From: Yao Qi To: Subject: [PATCH 0/5] MI notification on trace started/stopped (V3) Date: Tue, 22 Jan 2013 07:05:00 -0000 Message-ID: <1358838232-13319-1-git-send-email-yao@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain 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: 2013-01/txt/msg00505.txt.bz2 Hello, 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. This patch series is the V3 of this series. V2 was posted . Here are some changes in V3, - Introduce query mechanism on supported notifications - Introduce concept "annex" into remote notification, - Remove trace notes in MI notifications, suggested by Pedro in the review. - Combine observers 'trace-started' and 'trace-stoped' into one observer 'trace-changed'. Each patch is tested cumulatively on x86_64-linux with the combination {unix, native-gdbserver} x {sync, async}. Is it OK? -- 1.7.7.6