From owner-freebsd-hackers  Mon Dec  1 10:57:45 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA02392
          for hackers-outgoing; Mon, 1 Dec 1997 10:57:45 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from kai.communique.net (Kai.communique.net [204.27.67.90])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02387
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 1 Dec 1997 10:57:42 -0800 (PST)
          (envelope-from nectar@NECTAR.COM)
Received: (from smap@localhost)
	by kai.communique.net (8.8.8/8.8.7) id NAA19883;
	Mon, 1 Dec 1997 13:03:39 -0600 (CST)
X-Authentication-Warning: kai.communique.net: smap set sender to <nectar@NECTAR.COM> using -f
Received: from localhost.communique.net(127.0.0.1) by kai.communique.net via smap (V2.0)
	id xma019879; Mon, 1 Dec 97 13:03:30 -0600
Date: Mon, 1 Dec 1997 13:03:30 -0600 (CST)
From: Jacques Vidrine <nectar@NECTAR.COM>
X-Sender: nectar@kai.communique.net
To: Thomas Gellekum <tg@ihf.rwth-aachen.de>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: pthreads
In-Reply-To: <873ekdciyg.fsf@ghpc6.ihf.rwth-aachen.de>
Message-ID: <Pine.BSF.3.96.971201130040.17788C-100000@kai.communique.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


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
>