Re: My understanding of python2.1 and cthreads

2001-11-02 Thread Roland McGrath
You'll have to show the bits of code in question for us to help much. No program ought to be calling cthread_init. Initialization is dealt with just by linking in -lthreads. ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listi

My understanding of python2.1 and cthreads

2001-11-02 Thread James Morrison
Hello, I've been trying to get python2.1 to run on GNU/Hurd with cthreads enabled. python1.5 'worked' with cthreads on GNU/Hurd. However, python2.1 tries to use threads on startup if they are available. One of the very first things python2.1 does is try to allocat

Re: Python2.1

2001-11-01 Thread Roland McGrath
If you want to port anything to use cthreads, you'll have to spend some effort understanding in detail how startup and locking and so forth work in cthreads, and debug this stuff yourself. ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/

Python2.1

2001-11-01 Thread James Morrison
I have got python2.1 to compile with cthreads enabled, however, when I try to use said binary, it seg faults. Here is backtrace: Program received signal SIGSEGV, Segmentation fault. __libc_calloc (n=1, elem_size=20) at malloc.c:3832 3832malloc.c: No such file or directory. in