From owner-freebsd-questions@FreeBSD.ORG Fri Jan 19 20:34:04 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D50516A406 for ; Fri, 19 Jan 2007 20:34:04 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.freebsd.org (Postfix) with ESMTP id 9C2BA13C45E for ; Fri, 19 Jan 2007 20:34:02 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay7.apple.com (relay7.apple.com [17.128.113.37]) by mail-out3.apple.com (8.13.8/8.13.8) with ESMTP id l0JKY19R015493; Fri, 19 Jan 2007 12:34:01 -0800 (PST) Received: from relay7.apple.com (unknown [127.0.0.1]) by relay7.apple.com (Symantec Mail Security) with ESMTP id A86F73007F; Fri, 19 Jan 2007 12:34:01 -0800 (PST) X-AuditID: 11807125-a4a53bb000006e4c-ee-45b12b397dc6 Received: from [17.214.13.96] (unknown [17.214.13.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay7.apple.com (Apple SCV relay) with ESMTP id 9704A30060; Fri, 19 Jan 2007 12:34:01 -0800 (PST) In-Reply-To: <45B12364.903@passagen.se> References: <45B12364.903@passagen.se> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Fri, 19 Jan 2007 12:34:00 -0800 To: Roger Olofsson X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAA== Cc: freebsd-questions@freebsd.org Subject: Re: How to catch a memory leak? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2007 20:34:04 -0000 On Jan 19, 2007, at 12:00 PM, Roger Olofsson wrote: > The application vlc (found in ports) when run on FBSD 5.x and 6.x > behaves as if there's a memory leak somewhere hidden in it. [ ... ] > My question is how do I track down a possible memory leak and would > there be a tool to monitor (from outside the application) what > process that allocates memory and how much? Consider something like the valgrind port or dlmalloc. -- -Chuck