This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/53379] [4.7/4.8 Regression] No backtrace generated for array bounds violation
- From: "jb at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 20 Feb 2013 21:20:44 +0000
- Subject: [Bug fortran/53379] [4.7/4.8 Regression] No backtrace generated for array bounds violation
- Auto-submitted: auto-generated
- References: <bug-53379-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53379
--- Comment #11 from Janne Blomqvist <jb at gcc dot gnu.org> 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.