This is the mail archive of the
mailing list for the Cygwin project.
Re: [ATTN MAINTAINER] python
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 04 Mar 2015 19:22:29 +0100
- Subject: Re: [ATTN MAINTAINER] python
- Authentication-results: sourceware.org; auth=none
- References: <87a906yvft dot fsf at Rainer dot invalid> <87ioehg5ze dot fsf at Rainer dot invalid> <20150303223156 dot GC3213 at calimero dot vinschen dot de> <87twy1jnz0 dot fsf at Rainer dot invalid> <20150304091404 dot GD3213 at calimero dot vinschen dot de>
Corinna Vinschen writes:
> The problem here is how the Windows stack works. "Stack reserve" is the
> initial size of the reserved virtual memory space used for the stack of
> the main thread. By default that's 2 Megs.
There were in fact two threads at the point of the SEGV, one in the
kernel DLL with a very short stack and the other one with a lot of stack
in compile.c (IÂdon't know which one would be the main thread).
> However, the stack for the main thread has a problem. The way a new
> process is created, the main thread stack is jammed between certain
> other datastructures, in the address space from 0x30000 and 0x230000.
> Since the stack is growing top-down, there's nothing a process can do
> when the reserved stack space is exhausted. Except generating an
> exception STATUS_STACK_OVERFLOW. And then... what? There's no way to
> reserve more space below 0x30000 and even *if* it would be possible, it's
> only a mere 192K.
I'm just saying that a message like "stack overrun" or something of that
sort would have told me to go look for the stack size a lot earlier than
just a segfault. As far as building maxima goes the problem is solved
and I just posted here again in case Yaakov thinks that shouldn't have
happened or maybe increase the stack size for the next build.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER: