From owner-freebsd-threads@FreeBSD.ORG Thu Dec 15 09:50:09 2005 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2060A16A41F for ; Thu, 15 Dec 2005 09:50:09 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E4D743D66 for ; Thu, 15 Dec 2005 09:50:04 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBF9o4LV039281 for ; Thu, 15 Dec 2005 09:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBF9o46W039280; Thu, 15 Dec 2005 09:50:04 GMT (envelope-from gnats) Date: Thu, 15 Dec 2005 09:50:04 GMT Message-Id: <200512150950.jBF9o46W039280@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: David Xu Cc: Subject: Re: threads/90392: libc stdio memory leak with pthread X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Xu List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 09:50:09 -0000 The following reply was made to PR threads/90392; it has been noted by GNATS. From: David Xu To: bug-followup@freebsd.org, dhartmei@freebsd.org Cc: Subject: Re: threads/90392: libc stdio memory leak with pthread Date: Thu, 15 Dec 2005 17:45:11 +0800 This definitely is a bug in libc, in fact, not only memory leak, but also deadlock. Functions like fscanf, vfscanf will deadlock itself in threaded program, because __svfscanf() calls fread() which will recursively lock the FILE itself! Try following in threaded program: fscanf(stdin, s, "%3c", t); It should deadlock itself. I am fixing it now. David Xu