http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51852
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-01-14 00:36:19 UTC --- surely this is obvious, don't HßèMÕþÿøtxøtsø before you txøtsø ;) you could also try building with --enable-checking=valgrind or run cc1plus under gdb and provide a stack trace and the values of some local variables at the point it prints garbage - that might give more clues about the problem.
