Date: Mon, 1 Dec 1997 13:03:30 -0600 (CST) From: Jacques Vidrine <nectar@NECTAR.COM> To: Thomas Gellekum <tg@ihf.rwth-aachen.de> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: pthreads Message-ID: <Pine.BSF.3.96.971201130040.17788C-100000@kai.communique.net> In-Reply-To: <873ekdciyg.fsf@ghpc6.ihf.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Any clue as to the broken signals in 1.4 and 1.5b1? How did you build 1.5b1? In my build, the interpreter exist after thead.start_new_thread(), although the thread does run to completion. This isn't the behavior I expect, nor find on the Win32 platform. Anyone else out there have applications using pthreads other than Python? Jacques Vidrine <n@nectar.com> On 1 Dec 1997, Thomas Gellekum wrote: > Jacques Vidrine <nectar@NECTAR.COM> writes: > > > Hi, > > > > Where can I find a status of pthread support for FreeBSD-current? I've > > not had experience with them before, but I have attempted to compile > > Python 1.5b1 with thread support, and the resulting application is not > > stable (in particular I've had problems with signals and the thread APIs > > themselves). > > Python-1.4 seems to work with threads, except for the signals. All the > demos ran fine when I tested it. 1.5b1 is a different matter. There > are some modules that break when you compile with thread support, like > signal and fpectl. That's all I can say for now, I wanted to do some > more tests in the next few days. > > tg >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971201130040.17788C-100000>