From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19419 invoked by alias); 15 Oct 2009 17:18:09 -0000 Received: (qmail 19408 invoked by uid 22791); 15 Oct 2009 17:18:07 -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; Thu, 15 Oct 2009 17:18:02 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id AED8E13083; Thu, 15 Oct 2009 10:18:00 -0700 (PDT) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by mailhost4.vmware.com (Postfix) with ESMTP id A544AC9A96; Thu, 15 Oct 2009 10:18:00 -0700 (PDT) Message-ID: <4AD75806.9070705@vmware.com> Date: Thu, 15 Oct 2009 17:18:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Joel Brobecker CC: Hui Zhu , "gdb-patches@sourceware.org" Subject: Re: [RFA] let record_resume fail immediately on error References: <20090928160728.GB9003@adacore.com> <20090929212910.GG6362@adacore.com> <20091014021007.GO5272@adacore.com> <20091014024202.GQ5272@adacore.com> <20091015045834.GY5272@adacore.com> <20091015162326.GA5272@adacore.com> In-Reply-To: <20091015162326.GA5272@adacore.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00344.txt.bz2 Joel Brobecker wrote: >> I think stop with sigtrap looks not very well. So I change it to sigint. > > From a user perspective, either is confusing and, IMO, wrong. The program > did not receive any of these signals, so it seems like we're pretending > that they did. Can't we just have an error message "Error: unsupported > instruction, cannot continue from there", and just display the frame > where we stopped? Hui, try returning signal zero. GDB will just report that you stopped, without saying anything about a signal. Old trick of mine. ;-)