From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18280 invoked by alias); 16 Mar 2012 08:28:49 -0000 Received: (qmail 18254 invoked by uid 22791); 16 Mar 2012 08:28:45 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_KN X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Mar 2012 08:28:33 +0000 From: "kloedej at knmi dot nl" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52594] no traceback expected for explicit fortran stop command combined with -fbacktrace Date: Fri, 16 Mar 2012 08:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kloedej at knmi dot nl X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-03/txt/msg01383.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594 --- Comment #2 from Jos de Kloe 2012-03-16 08:28:11 UTC --- Thanks for your answer. Using stop 0 or stop 1 would indeed be a way around, but the awkward thing is that I do have some requirements to produce different values for the exit status for different error conditions. So using stop 1 everywhere is no solution for me. Anyway, this bug is just a feature request, so it is up to you developers to decide if you want to implement this or not.