Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "teawater" <teawater@gmail.com>
Cc: "Michael Snyder" <msnyder@vmware.com>,
	        "Pedro Alves" <pedro@codesourcery.com>,
	<gdb-patches@sourceware.org>
Subject: RE: [RFA] Patch to fix "reverse-next" command error
Date: Fri, 13 Feb 2009 16:07:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA06EC2DCA@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <daef60380902111858l3c60c4d3ha4a211b9442cf733@mail.gmail.com>

> -----Original Message-----
> From: teawater [mailto:teawater@gmail.com] 
> Sent: Wednesday, February 11, 2009 9:59 PM
> To: Marc Khouzam
> Cc: Michael Snyder; Pedro Alves; gdb-patches@sourceware.org
> Subject: Re: [RFA] Patch to fix "reverse-next" command error
> 
> Hi Marc,
> 
> I can't reproduce this issue with or without 
> "fix-reverse-plt-error.txt".
 
> Could you try it with CVS-head version and new Precord patch 
> in attachment?
> 
> Thanks,
> Hui

Thanks for putting all the patches in a single attachement, it was
much easier like that. (there was no patch 4.  Is it not needed
anymore?)

I'm still getting the bug.
I have HEAD from Feb 12th.
 + the Precord patches you sent.
 + fix-reverse-plt-error.txt
 + stopped.diff from Volodya (although it is not needed for this test)

I compile with
g++ (GCC) 4.1.2 20070115 (prerelease) (SUSE Linux)

My linux is (uname -a)
Linux camoc0002 2.6.16.53-0.16-smp #1 SMP Tue Oct 2 16:57:49 UTC 2007
i686 i686 i386 GNU/Linux

Again, here is the output.
Could it be related to my printf library?


GNU gdb (GDB) 6.8.50.20090212-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       #include <stdio.h>
2       int main()
3       {
4           char* cptr = "Thread 1";
5           int b[2] = {5,8};
6           b[0] = 6;   b[1] = 9;
7           printf("Thread 1, loop \n");
8           printf("Thread 2, loop \n");
9           printf("Thread 3, loop \n");
10          return 1;
(gdb) b main
Breakpoint 1 at 0x8048485: file a.cc, line 4.
(gdb) r
Starting program: /local/home/lmckhou/testing/a.out 

Breakpoint 1, main () at a.cc:4
4           char* cptr = "Thread 1";
(gdb) rec
(gdb) b 10
Breakpoint 2 at 0x80484cc: file a.cc, line 10.
(gdb) c
Continuing.
Thread 1, loop 
Thread 2, loop 
Thread 3, loop 

Breakpoint 2, main () at a.cc:10
10          return 1;
(gdb) rs
9           printf("Thread 3, loop \n");
(gdb) 
8           printf("Thread 2, loop \n");
(gdb) 

No more reverse-execution history.
main () at a.cc:4
4           char* cptr = "Thread 1";


  reply	other threads:[~2009-02-13 15:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22  9:00 teawater
2009-01-27 17:15 ` Marc Khouzam
2009-01-27 23:31   ` Marc Khouzam
2009-01-30 16:25     ` teawater
2009-02-11 19:55       ` Marc Khouzam
2009-02-12  2:59         ` teawater
2009-02-13 16:07           ` Marc Khouzam [this message]
2009-02-16 10:26             ` teawater
2009-02-16 19:10               ` Marc Khouzam
2009-02-17  3:58                 ` teawater
2009-02-17 13:10                 ` teawater
2009-03-02  6:11         ` teawater
2009-05-06  6:01 ` Hui Zhu
2009-05-11  7:07   ` Hui Zhu
2009-06-09  2:18     ` Hui Zhu
2009-06-15  2:45       ` Michael Snyder
2009-06-15  6:47         ` Hui Zhu
2009-06-15 15:37           ` Marc Khouzam
2009-06-15 18:04             ` Michael Snyder
2009-06-18 23:56               ` Michael Snyder

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=6D19CA8D71C89C43A057926FE0D4ADAA06EC2DCA@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.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