From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3898 invoked by alias); 24 Oct 2012 16:38:44 -0000 Received: (qmail 3562 invoked by uid 22791); 24 Oct 2012 16:38:41 -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; Wed, 24 Oct 2012 16:38:35 +0000 Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1TR3yU-0002lF-Il from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Wed, 24 Oct 2012 09:38:34 -0700 Received: from SVR-ORW-FEM-04.mgc.mentorg.com ([147.34.97.41]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 24 Oct 2012 09:38:33 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-04.mgc.mentorg.com (147.34.97.41) with Microsoft SMTP Server id 14.1.289.1; Wed, 24 Oct 2012 09:38:33 -0700 Message-ID: <50881981.7070308@codesourcery.com> Date: Wed, 24 Oct 2012 16:38:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: Hui Zhu CC: Subject: Re: [RFC] Target-defined breakpoints [3/9] notification async References: <50880350.1040309@mentor.com> In-Reply-To: <50880350.1040309@mentor.com> Content-Type: text/plain; charset="ISO-8859-1"; 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-10/txt/msg00463.txt.bz2 On 10/24/2012 11:03 PM, Hui Zhu wrote: > This patch is the extend for the notification function. > Current notification function cannot handle the packet when GDB doesn't > want to send or receive packet from the remote target. > This patch do the extend make GDB can handle the notification even if it > doesn't send or receive packet. Looks we have two set of 'async notification' stuff here :) I am trying to set up an infrastructure of 'async notification' in gdb, so that other components can use it. Patches are here, http://sourceware.org/ml/gdb-patches/2012-10/msg00404.html [RFC 0/7 V3]A general notification in GDB RSP It is general, not specific to any notifications, and scalable. We've probably have two internal cases of using it, 'trace status change' and 'stub/probe status change', so "Target-defined breakpoint" can use it easily as well. Do you mind if I suggest maintainers to review my 'async notification' patches first? Once they go in, we can rebase your patch on top of it. I am sure your patch will be shorter dramatically then. WDYT? Or if you find my 'async notification' doesn't meet your needs, let me know. -- Yao