Re: ELKS: Application Code, Data, Heap and Stack Size??

[Anonymous]

Chad Page writes:
> 
> 
>       There is (was?) some stack checking done at the system call level. 
> However, it's not 100% foolproof - if the program gets sp above the
> low-water mark after dipping into bss before the next system call it won't
> be detected.
> 
>       Now, if you had a magic # right after bss and checked that also,
> that would really improve the stack checking.
> 
>       - Chad
> 

It had just occured to me that this would be a good way of doing it, which
I will implement we go down the fixed stack, variable heap route.

Al