Stack size allocations
bobl at optushome.com.au
Sat May 7 17:03:47 CDT 2005
On Sat, 7 May 2005 10:06 pm, Alexandre Julliard wrote:
> Robert Lunnon <bobl at optushome.com.au> writes:
> > The first patch addresses a problem I have found where Windows
> > applications under wine exceed the allocated stack. By default wine
> > allocates the same 1MB stack that windows does but wine has a different
> > stack consumption that does windows, adding the wine translation layers,
> > possibly OGL then X calls on top of this.
> Actually Wine stack usage should be very similar to Windows. The real
> problem is that Xlib seems to allocate large amount of stack space in
> some cases; I believe this has improved lately, since it's obviously
> also a problem for threaded Unix apps, and we haven't had reports of
> stack overflows on Linux for a long time. What you probably want to do
> is just unconditionally add some more space on Solaris until the X
> libraries are fixed.
When I wrote this I was trying to maintain the "Standard windows behaviour" in
the first instance with stack space expansion occurring only in the abnormal
case (Where the app does have a stack depletion problem and therefore the env
var is set)
If the concensus is to add space unconditionally (#ifdef only for Solaris)
then I'm happy to do that.
More information about the wine-devel