Thomas Wouters wrote:
On Wed, Jul 26, 2000 at 11:05:21PM -0400, Fred L. Drake, Jr. wrote:
Peter Schneider-Kamp writes:
Could SMP be involved? Do you get the same on a non-SMP system? Do others have the same problem with SMP systems?
I think Barry may have access to an SMP Sparc machine; if so, we'll be checking it out there.
I have also seen test_fork1 failures on BSDI, using a SMP machine, but I haven't tried it on non-SMP (we don't have too many of those). However, all our BSDI kernels are the same, having been built for SMP. Meetings permitting (which is doubtful, today :-() I'll see if I can pin that down.
It would, however, be fairly peculiar if test_fork1 breaks on all SMP-supporting systems... I don't really recall a reason for thread semantics to change reliably based on kernel/cpu settings, and it would be silly for them to do so! But I'll admit threads are silly, period ;-)
Could you be more specific about which aspect of test_fork1.py fails ? After looking at the code it seems that it's not the os.fork() itself that is not working, but some particular combination of using os.fork() on a process with multiple threads running. If the latter is the case, then I'd propose to simply switch off threads for SMP machines (is there a compile time switch we could use for this ?) until we have figured out what causes the problem. -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/