This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/53379] [4.7/4.8 Regression] No backtrace generated for array bounds violation


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]