Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: paawan oza <paawan1982@yahoo.com>
To: Hui Zhu <teawater@gmail.com>, hefeweizen <horacio.sanchez@kit.edu>
Cc: gdb@sourceware.org
Subject: Re: gdb reverse debugging error
Date: Tue, 30 Mar 2010 07:01:00 -0000	[thread overview]
Message-ID: <79667.42051.qm@web112511.mail.gq1.yahoo.com> (raw)
In-Reply-To: <daef60381003292355l71d28702j549437c359a29f2d@mail.gmail.com>

so does it support
XMM, SSE and MMX insn support for x86 also ?
regards,
Oza.


----- Original Message ----
From: Hui Zhu <teawater@gmail.com>
To: hefeweizen <horacio.sanchez@kit.edu>
Cc: gdb@sourceware.org
Sent: Tue, March 30, 2010 12:25:36 PM
Subject: Re: gdb reverse debugging error

Hi horacio,

Thanks for you to report us about this issue.

0f0d is a 3dnow insn, Current gdb(7.1 cvs-head) is still not suport it.
But we are working on it now, please try the patch in
http://sourceware.org/ml/gdb-patches/2010-03/msg00944.html if you are
interesting with it.

Best regards,
Hui

On Sat, Mar 27, 2010 at 23:29, hefeweizen <horacio.sanchez@kit.edu> wrote:
>
>
>
> Hi,
>
> i started to try reverse debugging with gdb 7, followin the tutorial:
>
> http://www.sourceware.org/gdb/wiki/ProcessRecord/Tutorial
>
> and I thought, great!
>
> Then I started to debug a real program which gives an error at the end. So I
> run it with gdb, and I put a breakpoint just before the place I think the
> error appears. Then I type "record" in order to start to recrd actions for
> future reverse-debugging. But after some steps I get
>
> Process record doesn't support instruction 0xf0d at address 0x2aaaab4c4b4e.
> Process record: failed to record execution log.
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x00002aaaab4c4b4e in memcpy () from /lib64/libc.so.6
> (gdb) n
> Single stepping until exit from function memcpy,
> which has no line number information.
> Process record doesn't support instruction 0xf0d at address 0x2aaaab4c4b4e.
> Process record: failed to record execution log.
>
> Program received signal SIGABRT, Aborted.
> 0x00002aaaab4c4b4e in memcpy () from /lib64/libc.so.6
>
> Before I look at in in detail, I wonder if this feature is still buggy, or
> if I should start to record from the beginning.
>
> Where this "record" error happens, just an object is created as a copy of
> other:
>
> Thanks
>
> --
> View this message in context: http://old.nabble.com/gdb-reverse-debugging-error-tp28053097p28053097.html
> Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
>
>



      


  reply	other threads:[~2010-03-30  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27 15:30 hefeweizen
2010-03-30  6:56 ` Hui Zhu
2010-03-30  7:01   ` paawan oza [this message]
2010-03-30  7:03     ` Hui Zhu
2010-03-30  7:10       ` paawan oza

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=79667.42051.qm@web112511.mail.gq1.yahoo.com \
    --to=paawan1982@yahoo.com \
    --cc=gdb@sourceware.org \
    --cc=horacio.sanchez@kit.edu \
    --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