From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: <gdb@sourceware.org>
Subject: Wrong Reverse result
Date: Wed, 10 Jun 2009 16:50:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA0790D133@ecamlmw720.eamcs.ericsson.se> (raw)
Hi,
I'm getting a weird behaviour in reverse, where GDB
jumps to far backwards.
I have GDB HEAD from two weeks ago with the three
missing PRrecord patches applied (that were pinged
by Hui this very week).
I'm running on Ubuntu.
Is it me or can someone reproduce it?
(It happened during my presentation at the GCC summit,
so I have witnesses :-))
Thanks
Marc
GNU gdb (GDB) 6.8.50.20090522-cvs
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(gdb) l
1 void foo() {
2 return;
3 }
4
5 int main() {
6
7 foo(); // 1
8 foo(); // 2
9 foo(); // 3
10
(gdb) l
11 return 0;
12 }
(gdb) start
Temporary breakpoint 1 at 0x80483f7: file r.c, line 7.
Starting program: /home/marc/testing/a.out
Temporary breakpoint 1, main () at r.c:7
7 foo(); // 1
Current language: auto; currently c++
(gdb) record
(gdb) n
8 foo(); // 2
(gdb) n
9 foo(); // 3
(gdb) n
11 return 0;
(gdb) rn
9 foo(); // 3
(gdb) s
foo () at r.c:3
3 }
(gdb) rn
No more reverse-execution history.
main () at r.c:7
7 foo(); // 1
======== This is weird. Why does it go back to the top?
next reply other threads:[~2009-06-10 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 16:50 Marc Khouzam [this message]
2009-06-11 5:33 ` Hui Zhu
2009-06-11 8:28 ` Hui Zhu
2009-06-11 13:13 ` Marc Khouzam
2009-06-11 13:45 ` Ramana Radhakrishnan
2009-06-11 14:00 ` Joel Brobecker
2009-06-11 14:51 ` Marc Khouzam
2009-06-12 3:34 ` Hui Zhu
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=6D19CA8D71C89C43A057926FE0D4ADAA0790D133@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
/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