https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96486
Harald van Dijk <harald at gigawatt dot nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |harald at gigawatt dot nl
--- Comment #27 from Harald van Dijk <harald at gigawatt dot nl> ---
(In reply to Steve Kargl from comment #24)
> On Fri, Aug 07, 2020 at 08:35:49PM +0000, jussilehtola at fedoraproject dot
> org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96486
> >
> > --- Comment #21 from Susi Lehtola <jussilehtola at fedoraproject dot org>
> > ---
> > to repeat: libgfortran crashes when you try to read an environment variable
> > that is an empty string, in the case you have preallocated an array that is
> > the
> > proper size i.e. zero characters.
>
> to repeat: I cannot reproduce your issue. It does not crash.
> It exits with a runtime error.
It seems pretty clear to me that that runtime error is what "crash" refers to.
If you are merely wondering why a runtime error does not result in a backtrace
being printed for you: the default GCC 6+ behaviour is that runtime errors
cause a backtrace to be printed, but this can be changed by
-fbacktrace/-fno-backtrace compiler options and the GFORTRAN_ERROR_BACKTRACE
runtime environment variable. That is irrelevant to this bug though: the fact
that this program results in a runtime error is what this bug is about, not
which details get printed as a result of that runtime error. Your output shows
that you did manage to reproduce the issue just fine.
