Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: Marc Khouzam <marc.khouzam@ericsson.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: Tue, 17 Feb 2009 13:10:00 -0000	[thread overview]
Message-ID: <daef60380902162320o1c646ed0nf2dd169be44cda2c@mail.gmail.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA06EEF948@ecamlmw720.eamcs.ericsson.se>

Hi Marc,

Could you "wget
ftp://sourceware.org/pub/gdb/snapshots/current/gdb.tar.bz2" and patch
the patch in http://sourceware.org/ml/gdb-patches/2009-02/msg00344.html.


If you still get this issue.
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");

#Before the last rs command call command "set debug infrun 1"

(gdb)

No more reverse-execution history.

And post all output to me.  It will help me a lot.  :)


Thanks,
Hui




On Mon, Feb 16, 2009 at 23:16, Marc Khouzam <marc.khouzam@ericsson.com> wrote:
>
>
>> -----Original Message-----
>> From: teawater [mailto:teawater@gmail.com]
>> Sent: Monday, February 16, 2009 3:57 AM
>> 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 try it again.  This test is still OK with me.  Could remove
>> stopped.diff patch and try it again?
>> Or send me a stopped.diff patch?
>
> The stopped.diff patch was just checked in.
> You will actually have to update record.c as it no longer
> compiles with those new changes (small fix needed.)
>
> I updated to today's HEAD and I still get the problem.
> How did you turn on those traces to debug the problem?
>
> Thanks
>
> Marc
>
>


  parent reply	other threads:[~2009-02-17  7:21 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
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 [this message]
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=daef60380902162320o1c646ed0nf2dd169be44cda2c@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --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