From: teawater <teawater@gmail.com>
To: "Michael Snyder" <msnyder@vmware.com>
Cc: "Pedro Alves" <pedro@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [reverse/record] adjust_pc_after_break in reverse execution mode?
Date: Mon, 20 Oct 2008 23:36:00 -0000 [thread overview]
Message-ID: <daef60380810201636g3aa0e935r55eedbac1457e9a1@mail.gmail.com> (raw)
In-Reply-To: <48FCC413.3040506@vmware.com>
I think your mean is check breakpoint in address
read_pc()+gdbarch_decr_pc_after_break (gdbarch) in record_wait, right?
On Tue, Oct 21, 2008 at 01:46, Michael Snyder <msnyder@vmware.com> wrote:
> Pedro Alves wrote:
>
>> I believe the correct thing for the target to do is to
>> report `PC + decr_pc_after_breakpoint' on forward (replay or normal
>> forward)
>> breakpoint hits, if it is telling GDB that it succesfully
>> inserted a software breakpoint.
>
> Yeah, you and Daniel have both said essentially the same.
> And I think you're right.
>
> Hui, can you do this?
>
> Unfortunately, right now I think you are handling the
> breakpoints in record.c (which is architecture-agnostic).
> Maybe you'll have to check the decr_pc_after_break value.
>
>
next prev parent reply other threads:[~2008-10-20 23:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 1:11 Pedro Alves
2008-10-18 1:26 ` Michael Snyder
2008-10-18 3:09 ` Pedro Alves
2008-10-18 3:18 ` teawater
2008-10-18 8:42 ` Andreas Schwab
2008-10-19 14:28 ` teawater
2008-10-19 20:10 ` Daniel Jacobowitz
2008-10-18 3:07 ` teawater
2008-10-18 3:26 ` Pedro Alves
2008-10-19 22:44 ` Michael Snyder
2008-10-20 0:10 ` Pedro Alves
2008-10-20 0:44 ` Michael Snyder
2008-10-20 1:46 ` Daniel Jacobowitz
2008-10-20 12:10 ` Pedro Alves
2008-10-20 15:50 ` teawater
2008-10-20 17:44 ` Pedro Alves
2008-10-20 17:51 ` Michael Snyder
2008-10-20 23:36 ` teawater [this message]
2008-10-21 0:21 ` Pedro Alves
2008-10-21 0:56 ` teawater
2008-10-21 3:13 ` teawater
2008-10-21 6:52 ` teawater
2008-10-21 6:52 ` teawater
2008-10-23 23:28 ` Michael Snyder
2008-10-21 7:04 ` teawater
2008-10-21 18:36 ` Michael Snyder
2008-10-22 0:39 ` teawater
2008-10-23 23:32 ` Michael Snyder
2008-10-23 23:46 ` Pedro Alves
2008-10-23 23:55 ` Pedro Alves
2008-10-24 0:45 ` Michael Snyder
2008-10-24 0:43 ` Michael Snyder
2008-10-24 1:51 ` Pedro Alves
2008-10-24 8:11 ` teawater
2008-10-24 9:58 ` teawater
2008-10-25 7:08 ` teawater
2008-10-28 3:21 ` teawater
2008-10-29 1:24 ` Michael Snyder
2008-10-30 3:01 ` teawater
2008-10-30 12:21 ` Pedro Alves
2008-10-30 22:06 ` Michael Snyder
2008-10-30 21:44 ` Pedro Alves
2008-10-30 21:29 ` Michael Snyder
2008-10-31 13:04 ` teawater
2008-10-31 0:25 ` 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=daef60380810201636g3aa0e935r55eedbac1457e9a1@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.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