From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27471 invoked by alias); 16 Sep 2008 04:22:33 -0000 Received: (qmail 27461 invoked by uid 22791); 16 Sep 2008 04:22:32 -0000 X-Spam-Check-By: sourceware.org Received: from ti-out-0910.google.com (HELO ti-out-0910.google.com) (209.85.142.188) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 16 Sep 2008 04:21:58 +0000 Received: by ti-out-0910.google.com with SMTP id d10so1608814tib.12 for ; Mon, 15 Sep 2008 21:21:55 -0700 (PDT) Received: by 10.110.15.9 with SMTP id 9mr600513tio.50.1221538914922; Mon, 15 Sep 2008 21:21:54 -0700 (PDT) Received: by 10.110.42.9 with HTTP; Mon, 15 Sep 2008 21:21:54 -0700 (PDT) Message-ID: Date: Tue, 16 Sep 2008 04:22:00 -0000 From: teawater To: "Michael Snyder" , "Daniel Jacobowitz" Subject: Re: [reverse RFA] no singlestep-over-BP in reverse Cc: "gdb-patches@sourceware.org" In-Reply-To: <48CEAA05.8050006@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48CEAA05.8050006@vmware.com> 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: 2008-09/txt/msg00348.txt.bz2 I think maybe some reverse target (in the future?) need it. Someone already know it already deal the breakpoint. But the others will not know. Maybe I will change inside record to second type. If this single step affect some target, how about let target choice it with itself? Thanks, Hui On Tue, Sep 16, 2008 at 02:31, Michael Snyder wrote: > When we're stopped at a breakpoint and we want to > continue in reverse, we're not actually going to > execute the instruction at the breakpoint -- we're > going to de-execute the previous instruction. > > Therefore there's no need to singlestep before > inserting breakpoints. In fact it would be a bad > idea to do so, because if there is a breakpoint at > the previous instruction, we WANT to hit it. > > Note that this patch is to be applied to the reverse branch. > > 2008-09-15 Michael Snyder > > * infrun.c (proceed): No need to singlestep over a breakpoint > when resuming in reverse. > > Index: infrun.c > =================================================================== > RCS file: /cvs/src/src/gdb/infrun.c,v > retrieving revision 1.300.2.5 > diff -u -p -r1.300.2.5 infrun.c > --- infrun.c 5 Sep 2008 03:37:10 -0000 1.300.2.5 > +++ infrun.c 15 Sep 2008 18:28:29 -0000 > @@ -1226,11 +1226,17 @@ proceed (CORE_ADDR addr, enum target_sig > > if (addr == (CORE_ADDR) -1) > { > - if (pc == stop_pc && breakpoint_here_p (pc)) > + if (pc == stop_pc && breakpoint_here_p (pc) > + && target_get_execution_direction () == EXEC_FORWARD) > /* There is a breakpoint at the address we will resume at, > step one instruction before inserting breakpoints so that > we do not stop right away (and report a second hit at this > - breakpoint). */ > + breakpoint). > + > + Note, we don't do this in reverse, because we won't > + actually be executing the breakpoint insn anyway. > + We'll be (un-)executing the previous instruction. */ > + > oneproc = 1; > else if (gdbarch_single_step_through_delay_p (gdbarch) > && gdbarch_single_step_through_delay (gdbarch, > >