LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Torri <storri@torri.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Obtaining a list of memory address ranges allocated to processes
Date: Wed, 06 Dec 2006 17:56:26 -0600	[thread overview]
Message-ID: <1165449386.13079.30.camel@base.torri.org> (raw)

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?

Stephen


             reply	other threads:[~2006-12-06 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 23:56 Stephen Torri [this message]
2006-12-07  0:36 ` Remi Colinet
2006-12-07  7:10 ` Arjan van de Ven

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=1165449386.13079.30.camel@base.torri.org \
    --to=storri@torri.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Obtaining a list of memory address ranges allocated to processes' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).