From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Hui Zhu" <teawater@gmail.com>
Cc: <gdb@sourceware.org>, "Michael Snyder" <msnyder@vmware.com>
Subject: RE: Wrong Reverse result
Date: Thu, 11 Jun 2009 13:13:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA0790D648@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <daef60380906102233m5a1629bajc0a60944e432230@mail.gmail.com>
> -----Original Message-----
> From: Hui Zhu [mailto:teawater@gmail.com]
> Sent: June-11-09 1:34 AM
> To: Marc Khouzam
> Cc: gdb@sourceware.org; Michael Snyder
> Subject: Re: Wrong Reverse result
>
> I have reproduced this issue and find out the cause.
Great. Thanks for doing that so quick.
I forgot how to turn on those nice traces. Can you
remind me?
The traces don't mean much to me, but I can include them
in any future (if any :-)) issues.
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x8048361
> infrun: stepped into subroutine
> infrun: inserting step-resume breakpoint at 0x8048349
>
> stop_stepping is better.
>
> infrun: resume (step=0, signal=0), trap_expected=0
> infrun: prepare_to_wait
> infrun: target_wait (-1, status) =
> infrun: 10798 [process 10798],
> infrun: status->kind = no-history
> infrun: infwait_normal_state
>
> No more reverse-execution history.
> infrun: stop_stepping
> main () at 1.c:7
>
> On Thu, Jun 11, 2009 at 00:49, Marc
> Khouzam<marc.khouzam@ericsson.com> wrote:
> > 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).
>
> All of patches are not for prec, they are for reverse.
I realized that just after pressing 'send' :-)
> > 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 :-))
>
> I am not sure Michael in GCC summit or not. If so, you can let he fix
> it at there directly. :)
The summit is over now, but I did meet with Michael. It's nice to see
people face to face. I was able to put a bit of pressure on him
about reviewing the missing patches ;-). I'm sure that as soon as he
has time, he'll have a look at these four things.
Thanks Hui
marc
>
> Thanks for your help.
>
> Hui
>
> >
> > 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 prev parent reply other threads:[~2009-06-11 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 16:50 Marc Khouzam
2009-06-11 5:33 ` Hui Zhu
2009-06-11 8:28 ` Hui Zhu
2009-06-11 13:13 ` Marc Khouzam [this message]
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=6D19CA8D71C89C43A057926FE0D4ADAA0790D648@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--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