From: Shaun Jackman <sjackman@gmail.com>
To: binutils@sources.redhat.com
Subject: Finding the start and end of memory areas
Date: Thu, 23 Dec 2004 00:22:00 -0000 [thread overview]
Message-ID: <7f45d93904122216217855ef5f@mail.gmail.com> (raw)
First off, this posting is somewhat off-topic. My apologies in
advance. If anyone knows of a better forum for this topic, I'd
appreciate being pointed in the right direction. Now, on to my
question...
I'd like to find the start and end of the following memory areas
during run-time...
text
data
bss - &__bss_start to &__bss_end
heap - &__bss_end to sbrk(0)
(gap)
stack - stack pointer to ?
Presumably, they appear in that order in memory, so then end of one
should be the start of the next. Note that I'm doing this at run-time
by the program itself (introspection, as it were) and not with tools
like readelf and objdump. I've filled in the few values I know. If you
can provide any others I'd appreciate it.
If it affects the results, the target architectures are
i686-pc-linux-gnu and arm-elf.
Many thanks!
Shaun
next reply other threads:[~2004-12-23 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 0:22 Shaun Jackman [this message]
2004-12-23 11:15 ` Nick Clifton
2004-12-23 19:39 ` Shaun Jackman
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=7f45d93904122216217855ef5f@mail.gmail.com \
--to=sjackman@gmail.com \
--cc=binutils@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).