This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
gdb reverse debugging error
- From: hefeweizen <horacio dot sanchez at kit dot edu>
- To: gdb at sourceware dot org
- Date: Sat, 27 Mar 2010 08:29:54 -0700 (PDT)
- Subject: gdb reverse debugging error
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.