Hmm, this is strange, I'm 100% positive my binaries are always output of combo newest binutils + newest gcc, so those on my site are for sure build with binutils 2.20. Is there any way how to verify it?This bug was actually in the binutils and has been fixed in binutils-2.19.1-mint-20091017 and later.I am running latest builds of gcc 4.4.2 and binutils from vincent's site (well the gcc 4.4.2 is from mikro's site) and I still have the cout bug. All output stops after cout an int... Any ideas?
Virtually all the C++ libraries built with older binutils >=2.17 are wrong. In the case of the cout bug, libstdc++.a is the culprit.