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 libfortran/63930] New: libgfortran should use 'abort ()' instead of 'exit (2)' for run-time errors


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63930

            Bug ID: 63930
           Summary: libgfortran should use 'abort ()' instead of 'exit
                    (2)' for run-time errors
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: libfortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ludo at gnu dot org

libgfortran/runtime/error.c uses "exit (2)" in a few places to handle run-time
errors.  I would suggest replacing these calls with "abort ()".

The rationale is that using "abort" would make things more convenient for
users: one could inspect the core dump, or, when running the program in GDB,
directly get a prompt upon SIGABRT instead of having to resort to "catch
syscall exit_group".

Thanks.


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