mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Fu-hau Hsu <fhsu@ic.sunysb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory maps
Date: 03 Apr 2001 06:57:22 -0600	[thread overview]
Message-ID: <m1r8zaw37x.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.GSO.4.21.0104021611050.24682-100000@sparky.ic.sunysb.edu>
In-Reply-To: Fu-hau Hsu's message of "Mon, 2 Apr 2001 16:25:11 -0400 (EDT)"

Fu-hau Hsu <fhsu@ic.sunysb.edu> writes:

> Dear freinds:
> 
>  I have following questions about memory maps. I appreciate any
> suggestion.
> 
>  Q. (1)When a process is running, how can I get the range of data, stack,
>        and code segments, say the stack segment is from address 0x..... to
>        0x..... so do data segments and code segments?
>        PS: Under ELF format, there are several seperaed code and data
>            segments, but the process control table has only one pair of
>            pointers for each, Are the pointers still useful?


Sort of, you can currently confuse the elf loader with multiple bss segments.
The stack, and the brk pointer are still used. 

>     (2) /proc/*/maps will show us those info, but how does it get these
>        info? 

This is a reflection of what areas of memory the kernel sees.  In principle
every thing is now handled by mmap, and this /proc/maps is a reflection
of that.  See under the files in mm/*.c

Eric

      reply	other threads:[~2001-04-03 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 20:25 Fu-hau Hsu
2001-04-03 12:57 ` Eric W. Biederman [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=m1r8zaw37x.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=fhsu@ic.sunysb.edu \
    --cc=linux-kernel@vger.kernel.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®