From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23019 invoked by alias); 9 Mar 2011 16:09:02 -0000 Received: (qmail 23008 invoked by uid 22791); 9 Mar 2011 16:09:01 -0000 X-SWARE-Spam-Status: No, hits=-2.0 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, 09 Mar 2011 16:08:54 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 248BF2BAFBD; Wed, 9 Mar 2011 11:08:53 -0500 (EST) 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 7vY7NbMTabjr; Wed, 9 Mar 2011 11:08:53 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A87D62BAFBC; Wed, 9 Mar 2011 11:08:52 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 58B131459AD; Wed, 9 Mar 2011 20:08:47 +0400 (RET) Date: Wed, 09 Mar 2011 16:29:00 -0000 From: Joel Brobecker To: Jan Kratochvil Cc: Tom Tromey , Pedro Alves , gdb-patches@sourceware.org Subject: Re: Regression: [Re: RFC: change "program exited" message] Message-ID: <20110309160847.GW30306@adacore.com> References: <201103041913.09385.pedro@codesourcery.com> <201103041938.02711.pedro@codesourcery.com> <20110308065419.GA1239@host1.jankratochvil.net> <20110309153947.GA15507@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110309153947.GA15507@host1.jankratochvil.net> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2011-03/txt/msg00607.txt.bz2 > While the .exp testfile does not have too straightforward way to accept the > non-zero exit code I do not think a testfile should return with exit code > non-zero. But I failed to modify the .adb file such way, isn't there some > easy way, Joel? The non-zero status code is a consequence of a feature that I am testing in this testcase, which is an *unhandled* exception. So I need the exception to propagate all the way. So, I think we have no choice but to change the testcase itself, or enhance gdb_continue_to_end to be able to say that we expect the inferior to terminate with a non-zero status. I think the latter solution is probably preferable, because I'm pretty sure I'll mis-handle bareboard, or remote/gdbserver, or some other unusual configuration... I can look at that tomorrow. -- Joel