Stack size on 64-bit Cygwin

[Corinna Vinschen]

On Aug 19 14:36, Corinna Vinschen wrote:
> On Aug 19 07:43, Ryan Johnson wrote:
> > On 19/08/2013 7:39 AM, Corinna Vinschen wrote:
> > >On Aug 19 07:04, Ryan Johnson wrote:
> > >>So maybe emacs just had the incredibly bad luck to alloca() a large
> > >>buffer right at end-of-stack and then somehow managed to skip over
> > >>the 4 guard pages when accessing it?
> > >That's unlikely since alloca is designed to probe the stack in 4K
> > >steps.  And STATUS_STACK_OVERFLOW is translated to a SEGV by Cygwin's
> > >exception handler.
> > ... and yet somehow emacs managed to get around that protection
> > (unintentially), leading to all that fun over the last week. What
> > went wrong?
> 
> Good question.  I don't know.

And then again, Emacs is not exactly an STC for *any* problem...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20130819/6295e2e4/attachment.sig>