From owner-freebsd-current@FreeBSD.ORG Wed Aug 4 11:34:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20B8116A4CE for ; Wed, 4 Aug 2004 11:34:48 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 704D743D5A for ; Wed, 4 Aug 2004 11:34:46 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])i74BYfZV024615; Wed, 4 Aug 2004 14:34:43 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) i74AZPg5004293; Wed, 4 Aug 2004 13:35:25 +0300 (EEST) (envelope-from keramida@linux.gr) Received: (from keramida@localhost)i74AZOOL004292; Wed, 4 Aug 2004 13:35:24 +0300 (EEST) (envelope-from keramida@linux.gr) Date: Wed, 4 Aug 2004 13:35:24 +0300 From: Giorgos Keramidas To: ngl Message-ID: <20040804103524.GB4077@orion.daedalusnetworks.priv> References: <0ba301c47a11$fa028b80$0202000a@spirit> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0ba301c47a11$fa028b80$0202000a@spirit> cc: current@freebsd.org Subject: Re: POSIX Thread's locks failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2004 11:34:48 -0000 On 2004-08-04 16:58, ngl wrote: > > I use libpcap and libc_r under FreeBSD 5.2.1-p9, and i has faced a problem, > that sometimes pthread_mutex doesn't work properly. > > I'm getting packets from bpf with pcap_next function in one thread and > processing them in another. Both threads are using the same pthread_mutex > to synchronize. Everything works perfectly, but sometimes i get errors > could arise only if synchronization failed. A small program that exhibits the problem when run and a few details about the way we should run it while trying to reproduce the problem would be fine, IMHO.