[Bug fortran/52594] New: no traceback expected for explicit fortran stop command combined with -fbacktrace

["kloedej at knmi dot nl" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594

             Bug #: 52594
           Summary: no traceback expected for explicit fortran stop
                    command combined with -fbacktrace
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: kloedej@knmi.nl


I noticed that a full traceback is generated when gfortran executables exit
after an explicit stop command in the code.
Although useful in some cases, I would like to request an additional
commandline switch to block this behaviour.

My reasons:
-I am developing a collection of fortran software and am running routinely a
large number of unittests on them. A significant number of these unit tests
provoke the tool to stop with non-zero exit status (usually by inserting faulty
data that should trigger some safety checks in the software).
-I would like to easily discriminate real programming errors that can be
detected by gfortran (i.e. segmentation fault, illegal instruction, bus error
or floating-point exception, etc., as mentioned on the manpage), from these
explicit stop commands.
-the current situation where both types of conditions generate a full traceback
makes it hard to interpret the results because the interesting tracebacks get
lost in the large number of unwanted tracebacks from explicit stops.

Maybe you could consider implementing an option like: -fno-traceback-on-stop to
remedy this?