Segmentation Fault in wine cvs after 0.9

[Marcus Meissner]

On Sun, Nov 06, 2005 at 11:39:44PM +0100, Peter Beutner wrote:
> Mike McCormack schrieb:
> > zhilla wrote:
> >> http://gentoo-wiki.com/Safe_Cflags . if gentoo people claim these are
> >> safe cflags, and it worked until couple days ago, then something is
> >> definetly wrong, right?
> >
> > This is the wrong type of question for wine-devel, and better asked in
> > Gentoo forums or wine-users.
> heh?
> why should that be discussed in gentoo forums?
> 
> And it's not like -fomit-frame-pointer is such a high-risky optimization flag.
> Instead it is in general safe to use for 90% of applications out there( it basicly only
> prevents that you get some useful debug traces, by saving a few instructions)
> And like already stated, it used to work in wine too. Until some days ago.
> So why shouldn't that reported here?
> 
> Just for the record:
> I can confirm the segmentation fault(gcc 3.4.4), when compiled with -fomit-frame-pointer.
> I will try to find out which patch has caused this.

The problem could be a patch, or it could be something else.

While -fomit-frame-pointer is a no-risk option in other programs, this is not the case for WINE.

Why?

Because we call binary code.

And occasionaly this code assumes values in the %ebp register. The best
example is EXC_CallHandler() for instance, where windows code looks at
the %ebp framechain.

One reason while it is implemented in assembler now.

So please try current CVS after Robs last patch has been applied.

Ciao, Marcus