From owner-freebsd-current Wed Jan 3 8:54:35 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 08:54:30 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id D8DB637B402 for ; Wed, 3 Jan 2001 08:54:29 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14DrBD-0002dV-00 for ; Wed, 03 Jan 2001 17:54:27 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 14DrBC-0005xK-00 for ; Wed, 03 Jan 2001 17:54:26 +0100 Date: Wed, 3 Jan 2001 17:54:26 +0100 From: Nicolas Souchu To: freebsd-current@freebsd.org Subject: missing THREAD_UNLOCK in libc? Message-ID: <20010103175425.A22841@wiliam.alcove-int> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some troubleshootings with -current. A program that previously worked (-current of November) with -pthread now fails with an abort and a " in free(): error: recursive call" warning. I think that there may be some errors in my program and I'd like to know what was recently modified in libc or libc_r in order to track them down. While looking at the source of the warning in free(), I noticed that a THREAD_UNLOCK() may be missing in the case of a recursive call... Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message