From owner-freebsd-threads@FreeBSD.ORG Mon Sep 15 05:19:43 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D271F16A4BF for ; Mon, 15 Sep 2003 05:19:43 -0700 (PDT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5034443F85 for ; Mon, 15 Sep 2003 05:19:42 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by silver.he.iki.fi (8.12.9/8.11.4) with ESMTP id h8FCJdkO034802 for ; Mon, 15 Sep 2003 15:19:39 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <3F65AE5A.2030201@he.iki.fi> Date: Mon, 15 Sep 2003 15:19:38 +0300 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: malloc debugger X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 12:19:43 -0000 Does anyone have a recommendation which malloc debug library would be most suitable to be used with threads? I´ve had limited success with dmalloc but it seems to end in loops quite frequently for reasons I´ve not figured out. I´m looking for just simple leak accounting, fence checking would be a plus though. Pete