linux-kernel - Re: smap output - unnamed entries and heap

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] [day] [month] [year] [list]

Message-Id: <201103172322.49055.jerome@sysmic.org>
Date:	Thu, 17 Mar 2011 23:22:48 +0100
From:	Jérôme Pouiller <jerome@...mic.org>
To:	Aneesh Bhasin <contact.aneesh@...il.com>
Cc:	Pádraig Brady <P@...igbrady.com>,
	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

On Thursday 17 March 2011 12:46:13 Aneesh Bhasin wrote:
[..]
> 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..
A few years ago, I had a similar need. I made a small library which overload 
malloc (and free) and display caller (using backtrace_symbols function). 
Next I loaded it using LD_PRELOAD. The main problems are :
  * it only work for malloced memory (not mmaped memory)
  * It is difficult to interpred efficiently information provided. Name of 
caller may not be sufficient to understand why memory is allocated.

--
Jérôme Pouiller <jezz@...mic.org>
--
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/