From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30363 invoked by alias); 18 May 2012 15:02:40 -0000 Received: (qmail 30344 invoked by uid 22791); 18 May 2012 15:02:39 -0000 X-SWARE-Spam-Status: No, hits=-4.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED,TW_BG,TW_GM 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, 18 May 2012 15:02:26 +0000 From: "anlauf at gmx dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53379] [4.7/4.8 Regression] No backtrace generated for array bounds violation Date: Fri, 18 May 2012 15:04: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: anlauf at gmx dot de 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-05/txt/msg01820.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53379 --- Comment #5 from Harald Anlauf 2012-05-18 15:02:07 UTC --- (In reply to comment #3) > (In reply to comment #2) > > FWIW, if it is decided to change this, one could also consider changing > > runtime_error() and internal_error() in the same way, though one would need to > > audit the usage in libgfortran so that we don't generate a backtrace for a > > "file not found" or similar "benign" error. > > I agree that, at least by default, "file not found" shouldn't print a backtrace > - though one could still think of it with some aggressive backtrace > flag/environment variable. One option is too add a runtime_fatal() that gets called by those checks that are considered non-recoverable and deserve a backtrace if backtrace is requested. Examples are array-bounds violations, invalid pointers, etc. However, this requires an audit of the frontend.