From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9968 invoked by alias); 30 Mar 2010 07:03:30 -0000 Received: (qmail 9808 invoked by uid 22791); 30 Mar 2010 07:03:29 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG40,TW_CP X-Spam-Check-By: sourceware.org Received: from mail-pw0-f41.google.com (HELO mail-pw0-f41.google.com) (209.85.160.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 30 Mar 2010 07:03:24 +0000 Received: by pwi2 with SMTP id 2so5040222pwi.0 for ; Tue, 30 Mar 2010 00:03:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.40.6 with HTTP; Tue, 30 Mar 2010 00:03:02 -0700 (PDT) In-Reply-To: <79667.42051.qm@web112511.mail.gq1.yahoo.com> References: <28053097.post@talk.nabble.com> <79667.42051.qm@web112511.mail.gq1.yahoo.com> From: Hui Zhu Date: Tue, 30 Mar 2010 07:03:00 -0000 Received: by 10.142.61.35 with SMTP id j35mr874948wfa.124.1269932602215; Tue, 30 Mar 2010 00:03:22 -0700 (PDT) Message-ID: Subject: Re: gdb reverse debugging error To: paawan oza Cc: hefeweizen , gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-03/txt/msg00215.txt.bz2 See the title of this link. :) Hui On Tue, Mar 30, 2010 at 15:01, paawan oza wrote: > so does it support > XMM, SSE and MMX insn support for x86 also ? > regards, > Oza. > > > ----- Original Message ---- > From: Hui Zhu > To: hefeweizen > 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 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. >> >> > > > > > >