[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
My understanding of python2.1 and cthreads
From: |
James Morrison |
Subject: |
My understanding of python2.1 and cthreads |
Date: |
Fri, 2 Nov 2001 16:18:36 -0800 (PST) |
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 allocate a lock. When allocating
this lock
it checks if threads are initialized or not. They are not so
cthread_init()
is run then mutex_alloc() is run. calling mutex_alloc() is a macro
for
calloc(1,sizeof(struct mutex_t)). Somewhere in calling calloc the
program
seg faults. I seeing what happens when I do not run cthread_init();
I have made a simple program that does what I think python2.1
is
doing but it has no problems.
The back trace has not changed from my posting yesterday.
=====
James Morrison
University of Waterloo
Computer Science - Digital Hardware
2A co-op
http://hurd.dyndns.org
__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com
- My understanding of python2.1 and cthreads,
James Morrison <=