From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19581 invoked by alias); 14 Oct 2009 02:42:18 -0000 Received: (qmail 19571 invoked by uid 22791); 14 Oct 2009 02:42:17 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Oct 2009 02:42:12 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 27C8E2BAB52; Tue, 13 Oct 2009 22:42:11 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VbQbZJgRZqln; Tue, 13 Oct 2009 22:42:11 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id C46CB2BAB45; Tue, 13 Oct 2009 22:42:10 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 07D6BF58A0; Tue, 13 Oct 2009 19:42:02 -0700 (PDT) Date: Wed, 14 Oct 2009 02:42:00 -0000 From: Joel Brobecker To: Hui Zhu Cc: Michael Snyder , "gdb-patches@sourceware.org" Subject: Re: [RFA] let record_resume fail immediately on error Message-ID: <20091014024202.GQ5272@adacore.com> References: <4ABE5E8D.8080209@vmware.com> <20090928160728.GB9003@adacore.com> <20090929212910.GG6362@adacore.com> <20091014021007.GO5272@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-10/txt/msg00297.txt.bz2 > (gdb) record > (gdb) c > Continuing. > Process record doesn't support instruction rdtsc. > Process record doesn't support instruction 0xf31 at address 0x8048352. > Process record: failed to record execution log. > > Program received signal SIGABRT, Aborted. OK - I can see that there is a SIGABRT, and so I suspect that this SIGABRT is a consequence of the problem you're trying to fix. Can you explain the sequence of events that occur inside GDB that cause this SIGABRT? Can you also explain how you are fixing this problem? Again, from a copy of the GDB session *after* your patch, it looks like GDB is stuck on the unsupported instruction, and I'm not sure that this is an improvement. So I'm assuming that I am not understanding what your fix is doing. -- Joel