public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sfilippone at uniroma2 dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29649]  New: Force core dump on runtime library errors
Date: Mon, 30 Oct 2006 12:21:00 -0000	[thread overview]
Message-ID: <bug-29649-9410@http.gcc.gnu.org/bugzilla/> (raw)

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


             reply	other threads:[~2006-10-30 12:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 12:21 sfilippone at uniroma2 dot it [this message]
2006-10-30 12:24 ` [Bug libfortran/29649] " fxcoudert at gcc dot gnu dot org
2006-10-30 12:30 ` P dot Schaffnit at access dot rwth-aachen dot de
2006-10-31 15:54 ` burnus at gcc dot gnu dot org
2006-10-31 16:01 ` fxcoudert at gcc dot gnu dot org
2006-10-31 16:03 ` fxcoudert at gcc dot gnu dot org
2006-10-31 18:37 ` burnus at gcc dot gnu dot org
2006-10-31 19:10   ` Andrew Pinski
2006-10-31 19:10 ` pinskia at physics dot uc dot edu
2006-11-02 23:42 ` pinskia at gcc dot gnu dot org
2006-11-02 23:52 ` fxcoudert at gcc dot gnu dot org
2006-11-19 14:58 ` fxcoudert at gcc dot gnu dot org
2007-01-02 14:30 ` fxcoudert at gcc dot gnu dot org
2007-01-02 15:10 ` burnus at gcc dot gnu dot org
2007-01-05 14:03 ` fxcoudert at gcc dot gnu dot org
2007-01-05 21:25 ` patchapp at dberlin dot org
2007-01-12  6:48 ` fxcoudert at gcc dot gnu dot org
2007-01-18 12:54 ` burnus at gcc dot gnu dot org
2007-01-18 12:56 ` burnus at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29649-9410@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).