From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: "Ecos-List (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Where is my stack ?! (for my i386)
Date: Thu, 19 Oct 2000 17:29:00 -0000 [thread overview]
Message-ID: <5AF611D83988D4118ACF00E0B10400540557D8@mr-intranet.sdesigns.net> (raw)
Hi,
Where does the startup stack, the one used by cyg_start, is supposed to be ?
In the i386, it is located just in front of the startup code, and this is
very bad. At least i think the stack should be in a defined area of the
memory map and not in the void... Just where I was trying to put the idt,
the vsr table and the virtual vector tables.
How is this done in the other arch ? Where is the stack located ?
And is there any way to detect a stack overflow when it happens ?
Thanks
--
Fabrice Gautier
fabrice_gautier@sdesigns.com
next reply other threads:[~2000-10-19 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-19 17:29 Fabrice Gautier [this message]
2000-10-19 19:21 ` Jonathan Larmour
2000-10-19 20:33 Fabrice Gautier
2000-10-19 21:06 ` Jonathan Larmour
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=5AF611D83988D4118ACF00E0B10400540557D8@mr-intranet.sdesigns.net \
--to=fabrice_gautier@sdesigns.com \
--cc=ecos-discuss@sourceware.cygnus.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).