On 30 May 2002, Michael Hudson wrote:
Python doesn't create any threads. On Linux, I know that when you start your first thread, the thread library creates an extra thread for some internal reasons. Who knows what BSD does though.
I'm not sure either, but I have convinced myself that signal mask handling is just buggered on BSD when the program is compiled in a multi-threaded style (as, in simple C programs don't do what you (well, I) would expect). Note this isn't about actually using threads -- just using "cc -pthreads".
Now what do I do? Back my patch out? Not expose the functions on BSD? It works on Linux...
Cheers, M.
Can you forward me your simple C test case and a description of what you expect and what you get? I can take the issue up on the FreeBSD lists and see if I can get any clarifications. If I don't get anything back, then I guess we'll have to try not exposing the extra stuff on FreeBSD at least. Have you been able to test on Solaris or NetBSD/OpenBSD? (I'm assuming these are available in the SF compile farm). -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au | Snail: PO Box 370 andymac@pcug.org.au | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia