Re: gdb reverse debugging error

[Hui Zhu <teawater at gmail dot com>]

See the title of this link.  :)

Hui

On Tue, Mar 30, 2010 at 15:01, paawan oza <paawan1982@yahoo.com> wrote:
> 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.
>>
>>
>
>
>
>
>
>