Hi,
I'm afraid I'm not understanding this.....
I know that the code sized is fixed when an application is compiled, as is
the initialised and un-initilised data.
This gives us minimum code and data segment sizes.
We also need a stack, and maybe some heap space:-
Where does this go and how is it allocated?
If it is allocated at 'load' can it be resized (automatically or
manually)?
Is there any checking on the Stack Size (to prevent it over writing
the stack)?
Psion (on SIBO) seem to place a fixed stack at the bottom of the data
segment (which grows down towards DS:0000), then initialised data, then
un-initilised and then heap (which grows up). This has the advantage that
the 'hardware protection' can detect if the application writes outside it's
allocated data segment and halt the application. But the disadvantage that
the maximum stack size MUST be allocated at compile time.
Could this approach be taken with ELKS or do we need a resizable stack?
Simon Wood
Hardware Engineer
Pace Micro Technology plc
Victoria Road, Saltaire, Shipley
West Yorkshire, BD18 3LF
Tel : +44(0)1274 532000 Fax: +44(0)1274 532029
This E-Mail and any attachments hereto are strictly confidential and
intended solely for the addressee. If you are not the intended addressee
please notify the sender by return and delete the message. You must not
disclose, forward or copy this E-mail or attachments to any third party
without the prior consent of the sender.
