2.0b2 on Slackware 7.0
I just built and tested 2.0b2 on Slackware 7.0, and found that threads failed miserably. I got the message: pthread_cond_wait: Interrupted system call over & over (*hundreds* of times before I killed it) during one of the tests (test_fork1.py? it scrolled out of the scollback buffer, 2000 lines). If I configure it --without-threads it works great. Unless you need threads. uname -a says: Linux linux1.compile.sourceforge.net 2.2.14-5.0.14smp #1 SMP Sun Mar 26 13:03:52 PST 2000 i686 unknown ldd ./python says: libdb.so.3 => /lib/libdb.so.3 (0x4001c000) libdl.so.2 => /lib/libdl.so.2 (0x40056000) libutil.so.1 => /lib/libutil.so.1 (0x4005a000) libm.so.6 => /lib/libm.so.6 (0x4005d000) libc.so.6 => /lib/libc.so.6 (0x4007a000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) If anyone has any ideas, please send them along! I'll turn this into a real bug report later. -Fred -- Fred L. Drake, Jr. <fdrake at beopen.com> BeOpen PythonLabs Team Member
On Tue, Sep 26, 2000 at 04:32:21PM -0400, Fred L. Drake, Jr. wrote:
I just built and tested 2.0b2 on Slackware 7.0, and found that threads failed miserably. I got the message:
pthread_cond_wait: Interrupted system call
If anyone has any ideas, please send them along! I'll turn this into a real bug report later.
I'm inclined to nudge this towards a libc bug... The exact version of glibc
Slackware 7 uses would be important, in that case. Redhat has been using
glibc 2.1.3 for a while, which seems stable, but I have no clue what
Slackware is using nowadays (I believe they were one of the last
of the major distributions to move to glibc, but I might be mistaken.) And
then there is the possibility of optimization bugs in the gcc that compiled
Python or the gcc that compiled the libc/libpthreads.
(That last bit is easy to test though: copy the python binary from a working
linux machine with the same kernel major version & libc major version. If it
works, it's an optimization bug. If it works bug exhibits the same bug, it's
probably libc/libpthreads causing it somehow. If it fails to start
altogether, Slackware is using strange libs (and they might be the cause of
the bug, or might be just the *exposer* of the bug.)
--
Thomas Wouters
participants (2)
-
Fred L. Drake, Jr.
-
Thomas Wouters