Question on Stack Check in RTOS

Hi,

Nucleus offers an API for getting Task Information, which contains

minimum_stack information - Minimum amount of bytes left in the task's stack.


Since it is Minimum, does the Nucleus by default keep track on the Stack's Size at each task?

It seems very cycles-consuming to me.


I know that Nucleus offers an ENABLE_STACK_CHECK Compilation Flag, which

checks the Stack's usage at the beginning of each function in the file, but if the above

Information is available without this flag, then it makes the flag redundant.


Do you have an idea on the above, perhaps even from other RTOS?

Meaning, do RTOS'es normally keep track of the Minimum Bytes Left of each Task's Stack?

Thank you.
Last edited on
Do you mean the minimum value on the stack?

"Minimum bytes left" just doesn't compute, isn't that just "bytes left"?

I believe gcc stack check enabling (-fstack-check) is used to enable stack overflow checking.
Topic archived. No new replies allowed.