[ python-Bugs-881768 ] 2.3.3 hangs in test_fork1 and test_threadedtempfile

[SourceForge.net]

Bugs item #881768, was opened at 2004-01-21 22:28
Message generated for change (Comment added) made by mwh
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=881768&group_id=5470

Category: Threads
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: David Dyck (dcd)
Assigned to: Nobody/Anonymous (nobody)
Summary: 2.3.3 hangs in test_fork1 and test_threadedtempfile

Initial Comment:
make test hangs in 2.3.3 
 test_fork1 and test_threadedtempfile

go get test to complete I needed to 
 ./python -E -tt ./Lib/test/regrtest.py -l -x
test_fork1 -x test_threadedtempfile



----------------------------------------------------------------------

>Comment By: Michael Hudson (mwh)
Date: 2004-01-23 10:29

Message:
Logged In: YES 
user_id=6656

Fair enough, I suppose.  I doubt you'll get threads working
on such a system, though, as python tickles bugs in old
versions of pthreads.  You can try passing --disable-threads
(think that's the right incantation) to configure.

----------------------------------------------------------------------

Comment By: David Dyck (dcd)
Date: 2004-01-23 05:00

Message:
Logged In: YES 
user_id=53855

Since you asked.

It is quite simple to upgrade the kernel, and I've been
doing it since 1996.  It's a bit more difficult to upgrade
libc's so I've stuck with what's working.

It's gotten to the point that I've been trying to see how long
I can go before I have to upgrade to libc6.  I'm hoping that
Python is portable enough that I don't have to upgrade my
libc to get it working (I didn't have to upgrade my libc to
get Perl running :-)

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2004-01-22 11:03

Message:
Logged In: YES 
user_id=6656

You have a 2.4 kernel and are linking against libc *5*?!  Why?



----------------------------------------------------------------------

Comment By: David Dyck (dcd)
Date: 2004-01-22 01:41

Message:
Logged In: YES 
user_id=53855

thank you for reminding me of the questions I should have
answered
uname -a
Linux dd 2.4.25-pre6 #1 Fri Jan 16 13:23:13 PST 2004 i686
gcc -v
Reading specs from
/usr/lib/gcc-lib/i586-pc-linux-gnulibc1/egcs-2.91.66.1/specs
gcc version egcs-2.91.66.1 19990314/Linux (egcs-1.1.2
release)

libc.so.5.4.44

dd:lib$ which python
/usr/local/bin/python
dd:lib$ python -V
Python 2.3.3
dd:lib$ ldd /usr/local/bin/python
        libpthread.so.0 => /lib/libpthread.so.0 (0x4000c000)
        libdl.so.1 => /lib/libdl.so.1 (0x4001d000)
        libm.so.5 => /lib/libm.so.5 (0x40020000)
        libc.so.5 => /lib/libc.so.5 (0x40029000)

(my perl installation doesn't link
with any threads - I've don't
think any application on this linux
system have used pthread either)



----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2004-01-22 01:18

Message:
Logged In: YES 
user_id=31435

Of course these tests pass on all the platforms the 
developers and testers used, else 2.3.3 wouldn't have been 
released.

So the most important bits of info are missing:  which OS, and 
which C compiler and runtime, and which thread 
implementation, are you using?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=881768&group_id=5470