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 fortran/29649] New: Force core dump on runtime library errors


Running an application I got the following error 
Fortran runtime error: Attempt to allocate negative amount of memory.  Possible
integer overflow

This is not very helpful in debugging, as it gives no clue as to where in the
code it occurred. It would be extremely helpful to have a way to force a
backtrace produced, either explicitly via stderr (as Intel Fortran does for
code compiled with -traceback), or implicitly by producing a core dump.

Am not sure whether this should be filed against the front end (i.e.: a compile
time option) or the library (runtime environment variable? )

Salvatore


-- 
           Summary: Force core dump on runtime library errors
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sfilippone at uniroma2 dot it
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


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