From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83529 invoked by alias); 1 Sep 2016 17:06:10 -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 82568 invoked by uid 89); 1 Sep 2016 17:06:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=beside X-HELO: usplmg20.ericsson.net Received: from usplmg20.ericsson.net (HELO usplmg20.ericsson.net) (198.24.6.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Sep 2016 17:05:59 +0000 Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by (Symantec Mail Security) with SMTP id 3E.30.02488.C6168C75; Thu, 1 Sep 2016 19:12:15 +0200 (CEST) Received: from elxa4wqvvz1 (147.117.188.8) by smtps-am.internal.ericsson.com (147.117.188.81) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 1 Sep 2016 13:05:55 -0400 References: <20160831171406.24057-1-antoine.tremblay@ericsson.com> <20160831171406.24057-2-antoine.tremblay@ericsson.com> <3fdb7193-60c7-49c9-ccf5-bc040aa157ea@redhat.com> User-agent: mu4e 0.9.17; emacs 24.5.50.1 From: Antoine Tremblay To: Yao Qi CC: Pedro Alves , Antoine Tremblay , "gdb-patches@sourceware.org" Subject: Re: [PATCH 2/2] Enable range stepping for ARM on GDBServer In-Reply-To: Date: Thu, 01 Sep 2016 17:06:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2016-09/txt/msg00025.txt.bz2 Yao Qi writes: > [sigh, I am testing my arm range stepping patches today...] > Thanks for working on this :) > On Thu, Sep 1, 2016 at 4:59 PM, Pedro Alves wrote: >>>> >>>>> I'm sorry I can't be more helpful at the moment but I wanted to post >>>>> this issue before I have to leave for a while. >>>> >>>> Understood. Does enabling range stepping unblock something else? >>> >>> It would unblock ARM tracepoints, as per Yao's requirements... >> >> Tracepoints make gdbserver single-step and then not report the event >> to gdb, so I do see the parallel with range-stepping. Throwing >> while-stepping into the equation would make it even more clear. >> > > Range-stepping makes gdbserver single-step and then not report the event > to gdb if thread pc is within the range. It is similar to tracepoint, but much > simpler. > > Both range-stepping and tracepoing needs to remove reinsert_breakpoint > when gdbserver gets an event but doesn't report it back to gdb. However, > gdbserver doesn't do so now. That is the reason I believe we need to > support range-stepping first, and I am working on this (but interrupted by > 7.12 release). The draft patch attached removes reinsert_breakpoint when > gdbserver gets an event but not to report it back to gdb. > OK > Beside "removing reinsert_breakpoint on gdbserver internal event", we'd > better to think that "each backend unwinders don't have to worry about > unavailable data". I posted a draft here > https://sourceware.org/ml/gdb-patches/2016-05/msg00060.html, I need > some review comments. Pedro, > can you take a look? This is not a hard requirement for ARM tracepoint > support. Thanks for not making this one a hard requirement! Regards, Antoine