From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3658 invoked by alias); 16 Oct 2009 21:07:42 -0000 Received: (qmail 3649 invoked by uid 22791); 16 Oct 2009 21:07:41 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Oct 2009 21:07:35 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 5340D130FA; Fri, 16 Oct 2009 14:07:32 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost2.vmware.com (Postfix) with ESMTP id 368F68E79A; Fri, 16 Oct 2009 14:07:32 -0700 (PDT) Message-ID: <4AD8DF45.8090803@vmware.com> Date: Fri, 16 Oct 2009 21:55:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: burlen CC: "gdb@sourceware.org" , Hui Zhu Subject: Re: reverse execution References: <4AD8D8DC.2080904@gmail.com> In-Reply-To: <4AD8D8DC.2080904@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2009-10/txt/msg00277.txt.bz2 burlen wrote: > Is it possible to use reverse execution features on x86-64 linux > platform? I turned it on bad things happened. namely sigtrap then > sigabrt. it spit out these messages: > > Process record doesn't support instruction 0xf10 at address 0x7fffdda0dc77. > Process record: failed to record execution log. > > My session follows. Does this mean reverse execution isn't going to work > on this platform? or perhaps I have done something wrong in my attempt > to use the feature? > > Thanks > Burlen > > > (gdb) run > Starting program: /home/burlen/ext/ParaView/PV3-3.7/bin/pvserver > [Thread debugging using libthread_db enabled] > Listen on port: 11111 > Waiting for client... > Waiting for server... > Client connected. > ^C > Program received signal SIGINT, Interrupt. > 0x00007fffe31a66f3 in select () from /lib/libc.so.6 > (gdb) br vtkOOCFieldTracer::OOCIntegrateOne > Breakpoint 1 at 0x7fffdda0b591: file > /home/burlen/ext/ParaView/SciVisToolKit/vtkOOCFieldTracer.cxx, line 447. > (gdb) cont > Continuing. > > Breakpoint 1, vtkOOCFieldTracer::OOCIntegrateOne (this=0xa77570, > oocR=0x1fbff10, fieldName=0xed88b8 "vi", line=0x1fd2020, > tcon=0x7fffffffc480) at > /home/burlen/ext/ParaView/SciVisToolKit/vtkOOCFieldTracer.cxx:447 > 447 int w=0; > (gdb) target record > (gdb) disable 1 > (gdb) cont > Continuing. > Process record doesn't support instruction 0xf10 at address 0x7fffdda0dc77. > Process record: failed to record execution log. > > Program received signal SIGTRAP, Trace/breakpoint trap. > 0x00007fffdda0dc76 in FieldLine::GetSeedPoint (this=0x1fd2020, > p=0x7fffffffc2e0) at /home/burlen/ext/ParaView/SciVisToolKit/FieldLine.h:113 > 113 p[0]=this->Seed[0]; > (gdb) cont > Continuing. > Process record doesn't support instruction 0xf10 at address 0x7fffdda0dc77. > Process record: failed to record execution log. > > Program received signal SIGABRT, Aborted. > 0x00007fffdda0dc76 in FieldLine::GetSeedPoint (this=0x1fd2020, > p=0x7fffffffc2e0) at /home/burlen/ext/ParaView/SciVisToolKit/FieldLine.h:113 > 113 p[0]=this->Seed[0]; > (gdb) It's believed to be working on x86_64, but it's a brand new feature, so bugs are expected. I assume you are using gdb-7.0? Can you share your source code with us?