From owner-freebsd-questions@FreeBSD.ORG Wed Oct 1 15:57:05 2008 Return-Path: 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 016551065697 for ; Wed, 1 Oct 2008 15:57:05 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id B9D6D8FC17 for ; Wed, 1 Oct 2008 15:57:04 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id m91Fv3cP087246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 1 Oct 2008 10:57:04 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id m91Fv2l1087244; Wed, 1 Oct 2008 10:57:02 -0500 (CDT) (envelope-from dan) Date: Wed, 1 Oct 2008 10:57:02 -0500 From: Dan Nelson To: Ivan Voras Message-ID: <20081001155702.GK86326@dan.emsphone.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 7.1-PRERELEASE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-questions@freebsd.org Subject: Re: Process memory inspection 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: Wed, 01 Oct 2008 15:57:05 -0000 In the last episode (Oct 01), Ivan Voras said: > Hi, > > The top utility has SIZE and RES, but doesn't have what part of SIZE > is sysv shared memory. Is there something that can print out in > detail how a process uses / allocates its memory (I'm specifically > interested in sysvshm but there's also the stack & mmap)? You can get detailed process memory info from /proc//map , or in 7.1 and later, "procstat -v". I don't know how easy it is to identify which block is shared memory, though. -- Dan Nelson dnelson@allantgroup.com