public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas.L.Clune at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59654] Broken function table with complex OO use case
Date: Wed, 01 Jan 2014 04:53:00 -0000 [thread overview]
Message-ID: <bug-59654-4-py7aVpztll@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59654-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
--- Comment #4 from tlcclt <Thomas.L.Clune at nasa dot gov> ---
OK - had a bit of time waiting for the New Year countdown … so read up a bit
on valgrind.
A vanilla run under Linux with 4.9.0 gave the following, which seems
encouraging, albeit cryptic:
% gfortran -O0 -g allinone.F90
% valgrind ./a.out
==4724== Memcheck, a memory error detector
==4724== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==4724== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==4724== Command: ./a.out
==4724==
--4724-- WARNING: Serious error when reading debug info
--4724-- When reading debug info from /gpfsm/dhome/tclune/a.out:
--4724-- Ignoring non-Dwarf2/3 block in .debug_info
./a.out: error while loading shared libraries: libquadmath.so.0: cannot open
shared object file: No such file or directory
==4724== Jump to the invalid address stated on the next line
==4724== at 0x4DE: ???
==4724== by 0x400DEC7: _dl_signal_error (in /lib64/ld-2.11.1.so)
==4724== by 0x400CFD2: _dl_map_object_deps (in /lib64/ld-2.11.1.so)
==4724== by 0x40032B3: dl_main (in /lib64/ld-2.11.1.so)
==4724== by 0x4014979: _dl_sysdep_start (in /lib64/ld-2.11.1.so)
==4724== by 0x40013D0: _dl_start (in /lib64/ld-2.11.1.so)
==4724== by 0x4000B07: ??? (in /lib64/ld-2.11.1.so)
==4724== Address 0x4de is not stack'd, malloc'd or (recently) free'd
==4724==
==4724==
==4724== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==4724== Bad permissions for mapped region at address 0x4DE
==4724== at 0x4DE: ???
==4724== by 0x400DEC7: _dl_signal_error (in /lib64/ld-2.11.1.so)
==4724== by 0x400CFD2: _dl_map_object_deps (in /lib64/ld-2.11.1.so)
==4724== by 0x40032B3: dl_main (in /lib64/ld-2.11.1.so)
==4724== by 0x4014979: _dl_sysdep_start (in /lib64/ld-2.11.1.so)
==4724== by 0x40013D0: _dl_start (in /lib64/ld-2.11.1.so)
==4724== by 0x4000B07: ??? (in /lib64/ld-2.11.1.so)
==4724==
==4724== HEAP SUMMARY:
==4724== in use at exit: 0 bytes in 0 blocks
==4724== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4724==
==4724== All heap blocks were freed -- no leaks are possible
==4724==
==4724== For counts of detected and suppressed errors, rerun with: -v
==4724== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Thanks for helping with this!
>From gcc-bugs-return-438869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 01 05:02:58 2014
Return-Path: <gcc-bugs-return-438869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23454 invoked by alias); 1 Jan 2014 05:02:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23425 invoked by uid 48); 1 Jan 2014 05:02:54 -0000
From: "Thomas.L.Clune at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59654] Broken function table with complex OO use case
Date: Wed, 01 Jan 2014 05:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Thomas.L.Clune at nasa dot gov
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59654-4-3cOodWt3Ti@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg00011.txt.bz2
Content-length: 2083
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
--- Comment #5 from tlcclt <Thomas.L.Clune at nasa dot gov> ---
Ignore that output from Valgind. I was logged out between building and
running, and failed to reload the appropriate environment. With the correct
environment, I get a clean run from valgrind:
valgrind ./a.out
==9886== Memcheck, a memory error detector
==9886== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==9886== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==9886== Command: ./a.out
==9886==
--9886-- WARNING: Serious error when reading debug info
--9886-- When reading debug info from /gpfsm/dhome/tclune/a.out:
--9886-- Ignoring non-Dwarf2/3 block in .debug_info
--9886-- WARNING: Serious error when reading debug info
--9886-- When reading debug info from
/usr/local/other/SLES11.1/gcc/4.9/lib64/libgfortran.so.3.0.0:
--9886-- Ignoring non-Dwarf2/3 block in .debug_info
…
--9886-- Ignoring non-Dwarf2/3 block in .debug_info
--9886-- WARNING: Serious error when reading debug info
--9886-- When reading debug info from
/usr/local/other/SLES11.1/gcc/4.9/lib64/libquadmath.so.0.0.0:
--9886-- Ignoring non-Dwarf2/3 block in .debug_info
Error - incorrect number of tests were run.
==9886==
==9886== HEAP SUMMARY:
==9886== in use at exit: 1 bytes in 1 blocks
==9886== total heap usage: 22 allocs, 21 frees, 11,835 bytes allocated
==9886==
==9886== LEAK SUMMARY:
==9886== definitely lost: 0 bytes in 0 blocks
==9886== indirectly lost: 0 bytes in 0 blocks
==9886== possibly lost: 0 bytes in 0 blocks
==9886== still reachable: 1 bytes in 1 blocks
==9886== suppressed: 0 bytes in 0 blocks
==9886== Rerun with --leak-check=full to see details of leaked memory
==9886==
==9886== For counts of detected and suppressed errors, rerun with: -v
==9886== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
>From gcc-bugs-return-438870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 01 07:55:59 2014
Return-Path: <gcc-bugs-return-438870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3044 invoked by alias); 1 Jan 2014 07:55:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3003 invoked by uid 55); 1 Jan 2014 07:55:54 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59654] Broken function table with complex OO use case
Date: Wed, 01 Jan 2014 07:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59654-4-UaU337fZEk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg00012.txt.bz2
Content-length: 639
http://gcc.gnu.org/bugzilla/show_bug.cgi?idY654
--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Jan 01, 2014 at 05:02:53AM +0000, Thomas.L.Clune at nasa dot gov wrote:
>
> Ignore that output from Valgind. I was logged out between building and
> running, and failed to reload the appropriate environment. With the correct
> environment, I get a clean run from valgrind:
>
I like the other trace better. It suggested a memory corruption
problem. ;)
The trace here suggests to me that gfortran is losing a
pointer somewhere. Unfortunately, I don't know much
about the OO parts of gfortran.
next prev parent reply other threads:[~2014-01-01 4:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 1:25 [Bug fortran/59654] New: " Thomas.L.Clune at nasa dot gov
2014-01-01 1:27 ` [Bug fortran/59654] " Thomas.L.Clune at nasa dot gov
2014-01-01 4:02 ` kargl at gcc dot gnu.org
2014-01-01 4:27 ` Thomas.L.Clune at nasa dot gov
2014-01-01 4:53 ` Thomas.L.Clune at nasa dot gov [this message]
2014-01-01 13:40 ` [Bug fortran/59654] [OOP] " janus at gcc dot gnu.org
2014-01-01 14:13 ` Thomas.L.Clune at nasa dot gov
2014-01-01 23:25 ` janus at gcc dot gnu.org
2014-01-02 9:57 ` anlauf at gmx dot de
2014-01-02 11:08 ` janus at gcc dot gnu.org
2014-01-02 12:43 ` janus at gcc dot gnu.org
2014-01-02 13:51 ` janus at gcc dot gnu.org
2014-01-02 14:01 ` [Bug fortran/59654] [4.8/4.9 Regression] " janus at gcc dot gnu.org
2014-01-02 16:15 ` janus at gcc dot gnu.org
2014-01-02 17:27 ` janus at gcc dot gnu.org
2014-01-02 17:56 ` janus at gcc dot gnu.org
2014-01-02 20:51 ` Thomas.L.Clune at nasa dot gov
2014-01-02 21:59 ` janus at gcc dot gnu.org
2014-01-02 23:51 ` rouson at stanford dot edu
2014-01-03 9:15 ` burnus at gcc dot gnu.org
2014-01-04 13:27 ` Thomas.L.Clune at nasa dot gov
2014-01-04 16:47 ` janus at gcc dot gnu.org
2014-01-04 16:51 ` janus at gcc dot gnu.org
2014-01-04 18:54 ` dominiq at lps dot ens.fr
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-59654-4-py7aVpztll@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).