This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [reverse/record] adjust_pc_after_break in reverse execution mode?
- From: Pedro Alves <pedro at codesourcery dot com>
- To: Michael Snyder <msnyder at vmware dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, teawater <teawater at gmail dot com>
- Date: Mon, 20 Oct 2008 01:09:55 +0100
- Subject: Re: [reverse/record] adjust_pc_after_break in reverse execution mode?
- References: <200810180210.16346.pedro@codesourcery.com> <48FBB718.4040706@vmware.com>
On Sunday 19 October 2008 23:39:20, Michael Snyder wrote:
> After codgitating for a bit (that's "thinking" when you're over 50),
> I've decided that you're right.
>
> However, I have a new concern -- I'm worried about what it will do
> when it's replaying but going forward.
>
> Could you possibly revisit your test and see what it does
> if you record all the way to line 9 or 10, then back up
> to line 6, then continue with breakpoints at 6 and 7?
Eh, you're right. It's broken.
(gdb) record
(gdb) b 6
Breakpoint 2 at 0x8048352: file nop.c, line 6.
(gdb) b 7
Breakpoint 3 at 0x8048353: file nop.c, line 7.
(gdb) n
Breakpoint 3, main () at nop.c:7
7 asm ("nop");
(gdb) n
8 asm ("nop");
(gdb)
9 asm ("nop");
(gdb) n
10 }
(gdb) rc
Continuing.
Breakpoint 3, main () at nop.c:7
7 asm ("nop");
(gdb) rn
No more reverse-execution history.
main () at nop.c:6
6 asm ("nop");
(gdb) n
Breakpoint 2, main () at nop.c:6
6 asm ("nop");
(gdb)
8 asm ("nop");
(gdb)
9 asm ("nop");
(gdb)
--
Pedro Alves