http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827
--- Comment #23 from Tobias Burnus <burnus at gcc dot gnu.org> 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 :-(
