http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53379
--- Comment #2 from Janne Blomqvist <jb at gcc dot gnu.org> 2012-05-18 06:43:08 UTC --- AFAICS, this is an intentional change in behavior. When I proposed making backtracing enabled by default, there was some objections to the initial patch on the grounds that the backtracing was too aggressive. See http://gcc.gnu.org/ml/fortran/2011-05/msg00111.html 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. Or in other words, "error termination", as specified in the Fortran standard, should not lead to a backtrace. See also the comment in runtime/error.c that talks about this.
