From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4754 invoked by alias); 15 Oct 2009 04:38:20 -0000 Received: (qmail 4745 invoked by uid 22791); 15 Oct 2009 04:38:19 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-px0-f202.google.com (HELO mail-px0-f202.google.com) (209.85.216.202) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Oct 2009 04:38:15 +0000 Received: by pxi40 with SMTP id 40so874456pxi.24 for ; Wed, 14 Oct 2009 21:38:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.151.8 with SMTP id y8mr746757wfd.65.1255581494110; Wed, 14 Oct 2009 21:38:14 -0700 (PDT) In-Reply-To: <20091014024202.GQ5272@adacore.com> References: <4ABE5E8D.8080209@vmware.com> <20090928160728.GB9003@adacore.com> <20090929212910.GG6362@adacore.com> <20091014021007.GO5272@adacore.com> <20091014024202.GQ5272@adacore.com> From: Hui Zhu Date: Thu, 15 Oct 2009 04:38:00 -0000 Message-ID: Subject: Re: [RFA] let record_resume fail immediately on error To: Joel Brobecker Cc: Michael Snyder , "gdb-patches@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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/msg00329.txt.bz2 The important part is: (gdb) c Continuing. Program terminated with signal SIGABRT, Aborted. The program no longer exists. (gdb) record stop Process record is not started. The inferior is dead. "it looks like GDB > is stuck on the unsupported instruction, and I'm not sure that this > is an improvement." Stop is better than dead, right? Hui On Wed, Oct 14, 2009 at 10:42, Joel Brobecker wrote: >> (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. =A0Can you > explain the sequence of events that occur inside GDB that cause this > SIGABRT? =A0Can 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. =A0So I'm assuming that I am not understanding what > your fix is doing. > > -- > Joel >