> well, thanks for the hint, but: > compiling the "old" code (nested func call on return, recompiled only > memory/registry.c) with: > -mpreferred-stack-boundary=2 is working > -mpreferred-stack-boundary=3 exhibits the bug again > -mpreferred-stack-boundary=4 exhibits the bug again (of course that's the > default value) > > My first interpretation was wrong, but this stack alignment issue plays a role > in this bug... I don't have a clear idea why... well, recompiling whole Wine with -mpreferred-stack-boundary=2 exhibits the bug. So, this must be a a stack trashing issue, which existed before the suspected patch and that the patch did demonstrate... (or a badly written application) it'll be even harder to debug :-( sorry for the noise A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle
