http://bugs.winehq.org/show_bug.cgi?id=22925
--- Comment #7 from Wylda wylda@volny.cz 2010-05-31 11:01:52 --- (In reply to comment #6)
This indicates a memory corruption somewhere.
OK, i don't fear of valgrind+heap+relay and i'm also patient, but unfortunately this combinations never brought me luck. I'll go ahead. It have to come one day ;)
But before, looking at comment #4 i think only 1st scenario makes sence (we want a working wine, not broken, right?). So is there a chance to take the .o file from -O2 and put that into -O0 tree and build ntdll.dll.so from them (how??). Then we know the file, right?
I still have a feeling ("speculation") there is something wrong with wine's build system. What was the reason, that .44 did not compile when -O0 was used, but -O2 work arounded. This had to be a bug in build system, hadn't be?