From owner-freebsd-current Thu Jul 16 14:20:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17188 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:20:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17183 for ; Thu, 16 Jul 1998 14:20:09 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA06894 for ; Thu, 16 Jul 1998 14:19:53 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd006878; Thu Jul 16 14:19:45 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA03471 for current@freebsd.org; Thu, 16 Jul 1998 14:19:44 -0700 (MST) From: Terry Lambert Message-Id: <199807162119.OAA03471@usr07.primenet.com> Subject: PTHREADS: broken in current, stable? To: current@FreeBSD.ORG Date: Thu, 16 Jul 1998 21:19:44 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] 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 I have received a bug report from someone attempting to run LDAP that the libc_r implementation fails to allow LDAP to operate correctly. This may be nothing, but he is running a -stable system, recently upgraded. With the pending release of 2.2.7, this is protentially a rather large bug; I don't know of other programs that are really exercising the threads code. In the LDAP patches, I used PTHREAD_MUTEX_INITIALIZER to determine if the pthreads implementation was Darft 4, or if it was Draft 10 (Final standard). This bears on how a number of threads functions operate; most notably, a Draft 4 implementation is expected to take the address of an attribute pointer, whereas a Final standard implementation is expected to take an attribute pointer, as an argument to the pthread_create() function. It is apparent from the debugging information he sent me that the PTHREAD_MUTEX_INITIALIZER value is defined. I would caution *against* this definition, unless the threads library has been brought up to full Final Standard functionality. There is some possibility that this was pilot error on the part of the person sending the bug report; however, careful consideration should be made about pthreads functionality before assuming anything here. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message