From: Andrew Lunn <andrew@lunn.ch>
To: Tom Deconinck <t.deconinck@gmail.com>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Stack question
Date: Mon, 25 Feb 2008 15:18:00 -0000 [thread overview]
Message-ID: <20080225151754.GA20912@lunn.ch> (raw)
In-Reply-To: <e37cb5250802250641p774e11ddy8b79a344e9be77f0@mail.gmail.com>
On Mon, Feb 25, 2008 at 03:41:05PM +0100, Tom Deconinck wrote:
> Hi,
>
> Is there an easy way to know where in memory (exact address) the stack
> is located?
Which stack? There is the interrupt stack and the idle stack, which
could be the same. If you don't have your own main() function there is
also a system main() which has a stack. Plus all your threads have
stacks.
arm-elf-objdump --syms myprog.elf
or
arm-elf-nm myprog.elf
will show you the symbol table with addresses for all symbols.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-02-25 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 14:41 Tom Deconinck
2008-02-25 15:18 ` Andrew Lunn [this message]
2008-02-25 16:02 ` Tom Deconinck
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=20080225151754.GA20912@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sourceware.org \
--cc=t.deconinck@gmail.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).