Re: ELKS executable, time for a change?

[Alan Cox <alan@lxorguk.ukuu.org.uk>]

On Mon, 2002-10-28 at 12:14, Harry Kalogirou wrote:
> Also I would like to ask Al if he can explain how was he planning to
> support an enlarging stack? This is mentioned in mm/malloc.c. I
> personaly don't see a way for this to happen. Am I missing something?

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
	}