From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10552 invoked by alias); 20 Feb 2013 21:21:28 -0000 Received: (qmail 10320 invoked by uid 48); 20 Feb 2013 21:20:49 -0000 From: "jb at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53379] [4.7/4.8 Regression] No backtrace generated for array bounds violation Date: Wed, 20 Feb 2013 21:21: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: jb at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.7.3 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: 2013-02/txt/msg02112.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53379 --- Comment #11 from Janne Blomqvist 2013-02-20 21:20:44 UTC --- Looking at the frontend, calls to runtime_error_at are generated from gfc_trans_runtime_check() and gfc_trans_runtime_error(). I went through calls to these functions, and IMHO they all look like serious errors worthy of a backtrace, with the exception of ALLOCATE/DEALLOCATE failures when STAT= is not specified. In that case F2008 specifies that the processor must proceed with error termination, and printing a backtrace for this case would be a bit inconsistent with other cases of error termination.