Date: Sun, 25 May 2003 23:15:16 +1000 (EST) From: Andrew MacIntyre <andymac@bullseye.apana.org.au> To: freebsd-hackers@FreeBSD.org Cc: alane@FreeBSD.org Subject: setting stacksize in "initial" thread (pthreads, 4.8R) Message-ID: <20030525220222.K52253@bullseye.apana.org.au>
next in thread | raw e-mail | index | archive | help
I have a situation with a Python interpreter built from Python
CVS sources that is hitting the stack limit for the "initial" thread
imposed by libc_r: PTHREAD_STACK_INITIAL in
/usr/src/lib/libc_r/uthread/pthread_private.h is set to 1MB (0x100000).
Compiler optimisation settings do affect whether Python's internal stack
check activate before the hard limit bites, and more recent versions of
gcc (than the stock gcc in 4.8R) are more aggressive users of stack.
I have not been able to find any documented way to control the stacksize
of the "initial" thread either programmatically, via a compile/link
option or by way of a resource limit in login.conf. Is this possible
without rebuilding libc_r?
I don't yet have a 5.x install to check the situation - does the new
libthr/libkse setup differ in respect to the above?
Using the Linuxthreads port is a workaround for this situation,
but I'd rather that it not be necessary to rely on an extra
dependancy.
Cc'ed to the Python port maintainer for info.
Regards,
Andrew.
--
Andrew I MacIntyre "These thoughts are mine alone..."
E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370
andymac@pcug.org.au (alt) | Belconnen ACT 2616
Web: http://www.andymac.org/ | Australia
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030525220222.K52253>