Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: teawater <teawater@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [reverse RFA] no singlestep-over-BP in reverse
Date: Tue, 16 Sep 2008 18:40:00 -0000	[thread overview]
Message-ID: <48CFFCEA.7000002@vmware.com> (raw)
In-Reply-To: <daef60380809152110u663350abx76b283d519c5a09d@mail.gmail.com>

teawater wrote:
> 
> 
> On Tue, Sep 16, 2008 at 02:42, Daniel Jacobowitz <drow@false.org 
> <mailto:drow@false.org>> wrote:
> 
> 
>     If there is a breakpoint on the previous instruction, will you hit it
>     before or after de-executing that instruction?  It seems like this
>     logic should be somehow still necessary... but I can't put my finger
>     on when.
> 
> 
> I think is before exec the next instruction, the GDB will get breakpoint 
> trap.
> 
> But I found that there is a bug in inside record replay mode, I stop the 
> GDB after exec the instruction.

Aha, let's figure out a test for this question.
It's rather important.   ;-)

> Michael, how do you deal with the breakpoint in gdb-freeplay and vmware 
> record?

Both use simulated hardware breakpoints.  That is, they both
accept the Z0 message and emulate hardware breakpoint semantics
by watching the address of execution (one instruction at a time).


  parent reply	other threads:[~2008-09-16 18:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15 18:33 Michael Snyder
2008-09-15 18:43 ` Daniel Jacobowitz
2008-09-15 19:07   ` Michael Snyder
2008-09-15 21:15     ` Daniel Jacobowitz
2008-09-15 23:09       ` Michael Snyder
2008-09-16  0:09   ` Michael Snyder
2008-09-16  4:13   ` teawater
     [not found]   ` <daef60380809152110u663350abx76b283d519c5a09d@mail.gmail.com>
2008-09-16 18:40     ` Michael Snyder [this message]
2008-09-16  4:22 ` teawater
2008-09-16 15:04   ` teawater
2008-09-16 15:14     ` teawater
2008-09-16 15:22     ` Daniel Jacobowitz
2008-09-16 15:34       ` teawater
2008-09-16 15:35       ` teawater
2008-09-16 18:50       ` Michael Snyder
2008-09-16 18:45   ` Michael Snyder
2008-09-16 20:11     ` Joel Brobecker
2008-09-17  0:56       ` Michael Snyder
2008-09-17 15:44         ` teawater
2008-09-17 18:18           ` Michael Snyder
2008-09-17 15:32     ` teawater
2008-09-17 18:16       ` Michael Snyder
2008-09-18  6:39         ` teawater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48CFFCEA.7000002@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox