Hi!
okay. In my previous email I wanted to say, "knowing M$, I'd imagine they
limited it to 64k", but then thinking that stack size is determined by
the linker,
thought it made no sense. Now, though, the stack segment is determined by
the linker, the thread stack size is probably whole different s
Danny wrote:
> Could you apply this patch to src/binutils/configure.ac :
> [...]
> +AC_CHECK_HEADERS(iconv.h)
> [...]
> and then run
> autoreconf
> in the src/binutils directory.
eeho...@debian:~/src/cegcc-0.55/src/binutils$ autoreconf
configure.ac:26: error: Please use exactly Autoconf 2.59
Setting a large stack in a new thread is possible as documented. Example
included. The STACK_SIZE_PARAM_IS_A_RESERVATION macro has just been
added to SVN.
\network\x86> test3
\network\x86> type \temp\out.txt
In main
begin thread
Size : 33000
After memset
In deeper function
returning
e
Any kind of help is welcome at this point.
Actually I think the chkstk function used is in gcc's source code, in
the gcc/config/i386/cygwin.asm file I pointed to below.
I've been able to tweak the values in the headers that you mention by
using ld flags :
test2.o:test2.c
i386-min
Hi,
so, umm, what help are you asking for? :)
The chktsk goes down the stack and probes every page to make sure its
accessible before it is actually overrun (I guess a costly measure to avoid
stack overflows). I found its source code here:
http://read.pudn.com/downloads63/sourcecode/embed/220997
I've been poking in the stack limit problem that Johnny reported.
Test program attached, it can be used with e.g.
i386-mingw32ce-gcc -DSTACK_SIZE=6000 -o stack6000.exe stack.c
i386-mingw32ce-gcc -DSTACK_SIZE=66000 -o stack66000.exe stack.c
The stack6000 execution succeeds and leaves the expec
