public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Cc: "Ecos-List (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Where is my stack ?! (for my i386)
Date: Thu, 19 Oct 2000 19:21:00 -0000	[thread overview]
Message-ID: <39EFABB8.3043CA73@redhat.com> (raw)
In-Reply-To: <5AF611D83988D4118ACF00E0B10400540557D8@mr-intranet.sdesigns.net>

Fabrice Gautier wrote:
> 
> 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.

It's the startup stack. It's meant to exist very transiently and then get
zapped. It's size should be configurable, but it's no big deal if it is
discarded later. On some archs the interrupt stack is used as the startup
stack.

But it's certainly a bad place to put tables that you intend to stick
around.
 
> How is this done in the other arch ? Where is the stack located ?

Well, certainly in front of the startup code seems an unwise place. It
should be a fixed location in memory, which may later be reused. Why don't
you just look at the other archs?
 
> And is there any way to detect a stack overflow when it happens ?

Generally no, but I believe the x86 can be setup to do this?

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  reply	other threads:[~2000-10-19 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-19 17:29 Fabrice Gautier
2000-10-19 19:21 ` Jonathan Larmour [this message]
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=39EFABB8.3043CA73@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=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).