From: Robin Farine <acnrf@dial.eunet.ch>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] ARM startup stack & C++
Date: Wed, 08 Aug 2001 08:16:00 -0000 [thread overview]
Message-ID: <86ofpqshv0.fsf@halftrack.hq.acn-group.ch> (raw)
Hi gang,
I have got some stack overflow during execution of non-trivial static
initializers with C++ programs. The file vectors.S for ARM declares a startup
stack of 512 bytes when configured for separate interrupt stack. What do you
think I should do to get a big stack for initializers/finalizers?
1) Change the hardcoded 512 into 8192 ;-)
2) Add a configuration option for the startup stack size but nothing will use
this "big" area afterwards, correct?
3) Disable the separate interrupt stack but this probably has annoying
implications.
4) A completely different and wonderful solution?
Number 2 seems not too bad to me, what's your opinion?
Robin
next reply other threads:[~2001-08-08 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 8:16 Robin Farine [this message]
2001-08-08 8:32 ` Andrew Lunn
2001-08-08 9:13 ` Jonathan Larmour
2001-08-09 0:07 ` Robin Farine
2001-08-09 0:17 ` Robin Farine
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=86ofpqshv0.fsf@halftrack.hq.acn-group.ch \
--to=acnrf@dial.eunet.ch \
--cc=ecos-discuss@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).