From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31825 invoked by alias); 24 Oct 2010 11:10:40 -0000 Received: (qmail 31808 invoked by uid 22791); 24 Oct 2010 11:10:39 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,MISSING_MID 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; Sun, 24 Oct 2010 11:10:35 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: 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: Sun, 24 Oct 2010 11:10: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: 2010-10/txt/msg02018.txt.bz2 Message-ID: <20101024111000.D9TucvZijtVjoQwnOgr7oOf4HucyNjlpOfHVpMr6tsQ@z> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827 --- Comment #23 from Tobias Burnus 2010-10-24 11:10:18 UTC --- (In reply to comment #22) > Yes, I still get the error with later revisions. :-( > * Not putting use statements into "proper order" doesn't mean that the error > shows up, it randomly appears sometimes while you edit the code. When it appears, can you try (again) with valgrind (on f951) to see whether it shows some issues like uninitialised variables? I assume that there is some underlying memory access problem, e.g. an uninitialized variable or a dangling pointer. However, those errors tend to be difficult to track down - and without being able to either reproduce it nor having more information than "mio_component_ref(): Component not found", it is almost impossible to track down the error :-(