From owner-freebsd-current Tue Sep 16 06:25:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA23580 for current-outgoing; Tue, 16 Sep 1997 06:25:59 -0700 (PDT) Received: from freebsd1.cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA23573 for ; Tue, 16 Sep 1997 06:25:54 -0700 (PDT) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.8.5/8.8.5) id XAA04662; Tue, 16 Sep 1997 23:26:52 GMT From: John Birrell Message-Id: <199709162326.XAA04662@freebsd1.cimlogic.com.au> Subject: Re: Thread safe libc In-Reply-To: from Ian Hungerford at "Sep 16, 97 03:55:45 am" To: ianh@saturn-tech.com (Ian Hungerford) Date: Tue, 16 Sep 1997 23:26:51 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ian Hungerford wrote: > > > On Sun, 14 Sep 1997, Jordan K. Hubbard wrote: > > > Why don't you simply use libc_r ? That's what it's there for. :) > > I suppose I should have mentioned that I was looking at libc_r - there > are no _THREAD_SAFE tests in the net subdir (none that do anything, > anyway). :) Ian, Your assessment is correct. The net code in libc needs work to add the re-entrant calls which include the extra args to avoid the use of the static variables. And then work is needed to make the traditional functions with the static variables allocate those variables on a per-thread basis so that they behave in the same way they do in a sindle threaded program. > > --- > Ian > Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137