From: Arjan van de Ven <arjan@infradead.org>
To: Stephen Torri <storri@torri.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Obtaining a list of memory address ranges allocated to processes
Date: Thu, 07 Dec 2006 08:10:26 +0100 [thread overview]
Message-ID: <1165475426.3233.476.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1165449386.13079.30.camel@base.torri.org>
On Wed, 2006-12-06 at 17:56 -0600, Stephen Torri wrote:
> I am trying to create a custom ELF and Windows PE loader for the purpose
> of security research. I am having a difficult time finding how to
> allocate memory for a binary at the desired address in memory
> (especially if its non-relocatable). I would like to see why I cannot
> get memory allocated at the exact address request in the binary headers.
> Is there a program or system call that allows me to see a list of memory
> address ranges allocated to the running processes on a system?
Hi,
check the /proc/<pid>/maps and /proc/<pid>/smaps files... they have
exactly what you need
Greetings,
Arjan van de Ven
prev parent reply other threads:[~2006-12-07 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 23:56 Stephen Torri
2006-12-07 0:36 ` Remi Colinet
2006-12-07 7:10 ` Arjan van de Ven [this message]
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=1165475426.3233.476.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=storri@torri.org \
/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
all inboxes | Powered by JetHome®