From owner-freebsd-hackers Tue Apr 23 03:23:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA22807 for hackers-outgoing; Tue, 23 Apr 1996 03:23:27 -0700 (PDT) Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA22802 for ; Tue, 23 Apr 1996 03:23:25 -0700 (PDT) Received: from exalt.x.org by expo.x.org id AA13960; Tue, 23 Apr 96 06:22:53 -0400 Received: from localhost by exalt.x.org id GAA03612; Tue, 23 Apr 1996 06:22:53 -0400 Message-Id: <199604231022.GAA03612@exalt.x.org> To: hackers@freefall.FreeBSD.org Subject: Re: Help! I need info on pthreads. In-Reply-To: Your message of Tue, 23 Apr 1996 10:13:43 EST. <199604230013.KAA18978@melb.werple.net.au> Organization: X Consortium Date: Tue, 23 Apr 1996 06:22:52 EST From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have suddenly been informed that I must convert a significant > > piece of code to use pthreads. Since FreeBSD will be one of my > > test vehicles I need to know if the libc_r library under 2.1-stable > > and/or current is working. > > 2.2-current only. It works for me. If it doesn't work for _you_, let > me know. Watch out for libc functions that aren't re-entrant, though. You mean watch out for libc functions that aren't MT-safe. There's a big difference between being MT-safe and being reentrant. Reentrant means the function can be called in a signal handler, usually limited to system calls. MT-safe means the function can be called by more than one thread at a time. On other systems with threads there are MT-safe functions that aren't reentrant. -- Kaleb KEITHLEY