From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1226 invoked by alias); 30 Mar 2010 06:56:02 -0000 Received: (qmail 1217 invoked by uid 22791); 30 Mar 2010 06:56:01 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,SARE_MSGID_LONG40,TW_CP X-Spam-Check-By: sourceware.org Received: from mail-pv0-f169.google.com (HELO mail-pv0-f169.google.com) (74.125.83.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 30 Mar 2010 06:55:57 +0000 Received: by pvg2 with SMTP id 2so7199857pvg.0 for ; Mon, 29 Mar 2010 23:55:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.40.6 with HTTP; Mon, 29 Mar 2010 23:55:36 -0700 (PDT) In-Reply-To: <28053097.post@talk.nabble.com> References: <28053097.post@talk.nabble.com> From: Hui Zhu Date: Tue, 30 Mar 2010 06:56:00 -0000 Received: by 10.143.85.10 with SMTP id n10mr2482642wfl.106.1269932156103; Mon, 29 Mar 2010 23:55:56 -0700 (PDT) Message-ID: Subject: Re: gdb reverse debugging error To: hefeweizen Cc: 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/msg00213.txt.bz2 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. > >