This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/67365] Spurious address printed in backtrace
- From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 28 Aug 2015 09:11:34 +0000
- Subject: [Bug libfortran/67365] Spurious address printed in backtrace
- Auto-submitted: auto-generated
- References: <bug-67365-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67365
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-08-28
Ever confirmed|0 |1
--- Comment #1 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
Confirmed. This apparently has to do with FPE exceptions and signal handling,
but I don' know how. This was already present with the previous backtrace
implementation:
Backtrace for this error:
#0 0x7F75B429B467
#1 0x7F75B429BAAE
#2 0x7F75B37A264F
#3 0x4008DB in c at a.f90:7
#4 0x400856 in b at a.f90:12
#5 0x400828 in a at a.f90:17
#6 0x400833 in bt at a.f90:3
Floating point exception (core dumped)
(for example with gfortran 4.8.3). I will look into it.
If one makes a static executable and looks at the backtrace, the address
printed is in the vicinity of the following symbols (from "nm" output):
__libc_action
__restore_rt