From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27729 invoked by alias); 3 Feb 2011 00:11:08 -0000 Received: (qmail 27719 invoked by uid 22791); 3 Feb 2011 00:11:05 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Feb 2011 00:11:00 +0000 From: "townsend at astro dot wisc.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47546] Internal error - free_pi_tree(): Unresolved fixup X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: townsend at astro dot wisc.edu X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 03 Feb 2011 00:11:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-02/txt/msg00442.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546 --- Comment #15 from Rich Townsend 2011-02-03 00:09:57 UTC --- (In reply to comment #10) > (In reply to comment #9) > > Sounds like a Heisenbug -- it goes away when you look for it. Would it be worth > > bringing valgrind into the picture? > > Maybe. Could you try if it gives any useful output? ==13807== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==13807== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info ==13807== Command: gfortran-mp-4.6 -c foo.f90 ==13807== foo.f90:32.17: use hydro_speeds 1 Internal Error at (1): free_pi_tree(): Unresolved fixup ==13807== ==13807== HEAP SUMMARY: ==13807== in use at exit: 33,558 bytes in 82 blocks ==13807== total heap usage: 135 allocs, 53 frees, 35,636 bytes allocated ==13807== ==13807== LEAK SUMMARY: ==13807== definitely lost: 2,027 bytes in 31 blocks ==13807== indirectly lost: 75 bytes in 2 blocks ==13807== possibly lost: 4,085 bytes in 2 blocks ==13807== still reachable: 27,371 bytes in 47 blocks ==13807== suppressed: 0 bytes in 0 blocks ==13807== Rerun with --leak-check=full to see details of leaked memory ==13807== ==13807== For counts of detected and suppressed errors, rerun with: -v ==13807== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 3) Nothing particularly alarming -- although I guess those memory leaks might need fixing at some point. > Also: Can you reproduce the > error with my reduced test case in comment #8? > Done -- and I get the same fixup error. > > A different thought: Since 4.5 gives on the same test case > > mio_component_ref(): Component not found > > it may be related to PR45827.