From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30005 invoked by alias); 19 Mar 2012 04:48:19 -0000 Received: (qmail 29992 invoked by uid 22791); 19 Mar 2012 04:48:17 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00 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; Mon, 19 Mar 2012 04:47:55 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1S9UVe-00069Q-Qy from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Sun, 18 Mar 2012 21:47: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); Sun, 18 Mar 2012 21:47:54 -0700 Received: from [127.0.0.1] (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; Sun, 18 Mar 2012 21:47:53 -0700 Message-ID: <4F66BA7D.7050500@codesourcery.com> Date: Mon, 19 Mar 2012 04:48:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120310 Thunderbird/11.0 MIME-Version: 1.0 To: Subject: Re: [PATCH] Add autoload-breakpoints [0/7] References: <4F6450AF.5010609@mentor.com> In-Reply-To: <4F6450AF.5010609@mentor.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit 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-03/txt/msg00682.txt.bz2 On 03/17/2012 04:51 PM, Hui Zhu wrote: > Hi, > > There are patches to make GDB support autoload-breakpoints. For avoid of doubt, here is a high level description of these patches: Prior to GDB connects to remote stub, some breakpoints might have been already set in target, either by a prior GDB session or by the program itself through some special system API. When GDB connects to target, it should handle these existing breakpoints from remote stub. We call these breakpoints as "auotload breakpoints". > It is: > 1. it is set by the remote stub. > 2. The remote stub can control autoload-breakpoints any time even if GDB > is just control the inferior. The other use case we want to support in GDB is that inferior may delete/clear breakpoints on its own, and remote stub gets GDB notified, and GDB can take some actions accordingly. We believe such reliable report is useful to GDB, and generalize it, called "ReportAsync". The connection between "ReportAsync" and "autoload breakpoint" is when inferior/stub delete breakpoints, sends async report to GDB about removed breakpoints. -- Yao (齐尧)