From owner-freebsd-questions@FreeBSD.ORG  Sat Mar  6 03:31:25 2010
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 076CB106566B
	for <freebsd-questions@freebsd.org>;
	Sat,  6 Mar 2010 03:31:25 +0000 (UTC) (envelope-from yuri@rawbw.com)
Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45])
	by mx1.freebsd.org (Postfix) with ESMTP id D00D38FC15
	for <freebsd-questions@freebsd.org>;
	Sat,  6 Mar 2010 03:31:24 +0000 (UTC)
Received: from eagle.syrec.org (stunnel@localhost [127.0.0.1])
	(authenticated bits=0)
	by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id o263VOtJ017461
	for <freebsd-questions@freebsd.org>;
	Fri, 5 Mar 2010 19:31:24 -0800 (PST) (envelope-from yuri@rawbw.com)
Message-ID: <4B91CC8B.4010301@rawbw.com>
Date: Fri, 05 Mar 2010 19:31:23 -0800
From: Yuri <yuri@rawbw.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20100206)
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Is there a way to know how much memory is currently allocated?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: yuri@rawbw.com
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2010 03:31:25 -0000

Does FreeBSD malloc library provide any API way to know how many bytes 
are currently allocated by the current process?
Memory image size isn't adequate, since it's always much larger because 
of various reasons, like an extra-memory allocated for the needs of 
malloc library itself an also due to non-freed blocks, which are left 
allocated by the library.

Yuri