public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51197] [4.7 Regression] Backtrace information less useful
Date: Thu, 17 Nov 2011 20:25:00 -0000 [thread overview]
Message-ID: <bug-51197-4-gVkE3RQcMK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51197-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51197
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org 2011-11-17 20:04:07 UTC ---
(In reply to comment #0)
> Hi,
>
> the backtrace facility is less useful with 4.7 than with 4.6.
>
> Example:
>
> program backtrace
> implicit none
> print *, foo (0.0)
> contains
> function foo (x)
> real, intent (in) :: x
> real :: foo
> foo = 1 / x
> end function foo
> end program backtrace
>
>
> gfortran 4.7 (svn revision 181390, arch is i686-pc-linux-gnu):
>
> % /opt/gcc/4.7/bin/gfortran -g -fbacktrace gfcbug113.f90
> -ffpe-trap=zero,overflow,invalid -static-libgfortran
> % ./a.out
>
> A fatal error occurred! Backtrace for this error:
> #0 0x80588BF in _gfortrani_show_backtrace at backtrace.c:261
> #1 0x80494B7 in _gfortrani_backtrace_handler at compile_options.c:46
> #2 0xFFFFE3FF
> #3 0x80493B3 in foo at gfcbug113.f90:8
> #4 0x804940B in backtrace at gfcbug113.f90:3
> Floating point exception (core dumped)
>
>
> With gfortran 4.6:
>
> Program received signal 8 (SIGFPE): Floating-point exception.
>
> Backtrace for this error:
> + [0xffffe400]
> + function foo (0x80494B3)
> at line 8 of file gfcbug113.f90
> + function backtrace (0x804950C)
> at line 3 of file gfcbug113.f90
> + /lib/libc.so.6(__libc_start_main+0xe5) [0xb7641705]
>
>
> Same for SIGSEGV etc. It would be nice if I got back
> the old behaviour where the actual error is displayed.
> I'm not always good at guessing...
>
What exactly do you want?
In 4.7, the last line of the backtrace is
"Floating point exception (core dumped)".
That matches the first line from 4.6
"Program received signal 8 (SIGFPE): Floating-point exception."
In 4.7, the line
#3 0x80493B3 in foo at gfcbug113.f90:8
contains all of the information from 4.6
+ function foo (0x80494B3)
at line 8 of file gfcbug113.f90
--
steve
next prev parent reply other threads:[~2011-11-17 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 20:17 [Bug fortran/51197] New: " anlauf at gmx dot de
2011-11-17 20:25 ` kargl at gcc dot gnu.org [this message]
2011-11-17 20:55 ` [Bug fortran/51197] " anlauf at gmx dot de
2011-11-18 7:34 ` jb at gcc dot gnu.org
2011-11-18 14:09 ` burnus at gcc dot gnu.org
2011-11-18 19:51 ` anlauf at gmx dot de
2011-11-23 20:31 ` anlauf at gmx dot de
2011-11-23 21:00 ` anlauf at gmx dot de
2011-12-05 14:23 ` rguenth at gcc dot gnu.org
2011-12-06 14:04 ` rguenth at gcc dot gnu.org
2012-01-09 19:54 ` burnus at gcc dot gnu.org
2012-01-09 19:55 ` burnus at gcc dot gnu.org
2012-01-10 9:33 ` burnus at gcc dot gnu.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-51197-4-gVkE3RQcMK@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).