lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=gN=DOU9bQtqdr1s44y5QgLn0W9_oRb9JTMWNa@mail.gmail.com>
Date:	Thu, 17 Mar 2011 17:16:13 +0530
From:	Aneesh Bhasin <contact.aneesh@...il.com>
To:	Pádraig Brady <P@...igbrady.com>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	linux-newbie <linux-newbie@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: smap output - unnamed entries and heap

2011/3/16 Pádraig Brady <P@...igbrady.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.

I did try that script. Unfortunately, I not only want the memory used
for my program but also, which library is contributing to that memory.
To that end, I have written a small script which parses the smap
output in a format more suitable for my analysis.

However, as I wrote earlier, there a lot of anonymous memory regions
listed in smap output (with permission rwxp) - and I do not know of
any way in which I could associate these memory mapping to a
particular library..

Any pointers in this regard will be highly appreciated :)

Regards,
Aneesh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ