http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47546
--- Comment #15 from Rich Townsend <townsend at astro dot wisc.edu> 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.
