From: Harry Kalogirou <harkal@gmx.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: ELKS executable, time for a change?
Date: 28 Oct 2002 20:52:26 +0200 [thread overview]
Message-ID: <1035831066.5491.106.camel@cool> (raw)
In-Reply-To: <1035810496.2067.7.camel@irongate.swansea.linux.org.uk>
> If you have code to detect stack overflows then you can do it with a bit
> of compiler help. It makes things a lot more expensive so I question
> whether it should be done.
>
> Basically your entry code starts to look like
>
> function_entry:
> if(new frame wont fit on stack)
> {
> alloc new stack segment
> push old esp to new stack
> push args to new stack
> call function_entry
> fix stack
> pop old stack segment
> free newer stack segment
> ret
> }
>
>
Well, I think I can live with the fixed stack then!
Harry
next prev parent reply other threads:[~2002-10-28 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 12:14 ELKS executable, time for a change? Harry Kalogirou
2002-10-28 13:08 ` Alan Cox
2002-10-28 18:52 ` Harry Kalogirou [this message]
[not found] ` <20021028121918.GA29181@pulsion.ecs.soton.ac.uk>
2002-10-28 18:52 ` Harry Kalogirou
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 18:51 Harry Kalogirou
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=1035831066.5491.106.camel@cool \
--to=harkal@gmx.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-8086@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.