From owner-freebsd-current Mon Jun 8 17:55:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16259 for freebsd-current-outgoing; Mon, 8 Jun 1998 17:55:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16244 for ; Mon, 8 Jun 1998 17:55:26 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id KAA09481; Tue, 9 Jun 1998 10:58:34 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199806090058.KAA09481@cimlogic.com.au> Subject: Re: Threads library bug In-Reply-To: <199806081841.LAA13449@usr04.primenet.com> from Terry Lambert at "Jun 8, 98 06:41:08 pm" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 9 Jun 1998 10:58:34 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > This appears to be a problem with the dbm routines using the > libc_r system calls to do their thing? > > I am attempting to identify the precise problem, but you should not > expect a fix for a while. Check for a read or write with nbytes = 0. I'm about to commit a fix for this. This is the problem referred to on HighWind's download page (http://www.highwind.com/). There is also a big commit coming that will make the file descriptor lock tracking optional at libc_r compile time. This change also adds optional lock tracking to the spinlocks. The commit will include Alpha bits too. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message