Recompiling everything with gcc-3.2 has solved the problem for me.  It was
100% reproducible before.

This bug should be reassigned either to kernel-source-2.4.21 or gcc-3.3, but
I don't know which.  Copying both maintainers.

-- 
 - mdz


Reply via email to