https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63930
Harald Anlauf <anlauf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gmx dot de
--- Comment #2 from Harald Anlauf <anlauf at gmx dot de> ---
I think that there is a fundamental need to rewrite the handling of
runtime errors in gfortran. Since 4.7 I do often not get useful
backtraces with certain kinds of fatal errors like array-bounds
violation, see PR/53739. I use the patch I suggested there in my
private installations, but this doesn't help my colleagues at work.
I think a fatal runtime error does not require a nice termination
of the program, including closing of files etc.
However, this might require a general review - and classification -
of runtime errors:
- fatal (illegal operations like bad pointers/addresses etc.)
- severe (e.g. failed ALLOCATE?)
- soft (e.g. "file not found" in an OPEN statement)
I'm not sure where I'd place floating point exceptions; their
severity might even be configurable.
(Note: I'm writing this as nobody seems to care about PR/53739).
