http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52544
--- Comment #6 from Rodrigo Campos <rodrigo at sdfg dot com.ar> --- Actually, I recently find out that the memory corruption thing was not a GCC bug. It was a really weird error that only appears in the library if you do a print to stdout (not stderr) before some thing happens. And when I added a print compiling without -finstrument-functions, I did not added at the **very** beginning (but after some other thing, if not you will not hit the bug) and when compiling with "-finstrument-functions" it was added there. So I did not hit this weird bug when I tried to :) So I'm just hitting the bug originally reported with the same symptoms, sorry for the noise! If I can help in any way, please let me know :-) Thanks a lot, Rodrigo
