From: "Pádraig Brady" <P@draigBrady.com>
To: Aneesh Bhasin <contact.aneesh@gmail.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-newbie <linux-newbie@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: smap output - unnamed entries and heap
Date: Wed, 16 Mar 2011 14:09:00 +0000 [thread overview]
Message-ID: <4D80C47C.80300@draigBrady.com> (raw)
In-Reply-To: <AANLkTikU_kPOoNv6gJiPOsmrkFDddTLQ-0--wViYyFxj@mail.gmail.com>
On 16/03/11 05:19, Aneesh Bhasin wrote:
> Also, is there a way in linux (without using
> dedicated tools like valgrind), to see how much heap or anonymous
> memory is attributed to code arising from a particular library/binary
You might find ps_mem.py useful.
If parses smaps and reports RAM usage of a program
http://www.pixelbeat.org/scripts/ps_mem.py
cheers,
Pádraig.
next prev parent reply other threads:[~2011-03-16 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 9:01 smap output - unnamed entries and heap Aneesh Bhasin
2011-03-15 16:14 ` Randy Dunlap
2011-03-16 5:19 ` Aneesh Bhasin
2011-03-16 14:09 ` Pádraig Brady [this message]
2011-03-17 11:46 ` Aneesh Bhasin
2011-03-17 22:22 ` Jérôme Pouiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D80C47C.80300@draigBrady.com \
--to=p@draigbrady.com \
--cc=contact.aneesh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox