Segmentation Fault in wine cvs after 0.9

[Peter Beutner]

Mike McCormack schrieb:
> Peter Beutner wrote:
>> 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
> 
> If it fails for 10% of applications out there, then it's *not* safe!
The question is how often it only exposes a bug in the application(like in this case). ;)

> 
> (it basicly only prevents that you get some useful debug traces, by
> saving a few instructions)
> 
> I think turning off the debugging features of Wine isn't such a great
> idea, and not something that should be encouraged.  The more people that
> do that, the more useless crash reports Wine developers will get.
On the other hand the possibility to optimize wine isn't that bad either.
So just tell the users to send only crash reports from builds with debugging infos enabled.;)

>> And like already stated, it used to work in wine too. Until some days
>> ago.
>> So why shouldn't that reported here?
> 
> If somebody wants to report that an unsupported flag makes Wine not
> work, then he should figure out the exact patch and flag combination
> that caused the regression, and that's the information that should be
> posted to WineHQ.
then why not tell him that?
Besides there is nowhere stated that there are only certain supported compiler flags which
you should use.

> 
>> 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.
>
> That would be a great idea.
Somebody was faster, there was just sent a patch which fixes the problem.
http://www.winehq.org/pipermail/wine-patches/2005-November/021883.html

> 
> Mike
> 
> 
>