Skip to main content

Why does TASK.STacK show 100% stack usage for all tasks? - Knowledgebase / OS-aware debugging - Lauterbach Support

Why does TASK.STacK show 100% stack usage for all tasks?

TRACE32 OS awareness provides the start and end addresses of each task’s stack (low and high). To determine stack usage, TRACE32 scans the memory within this range and compares its contents against a predefined fill pattern.

For example, in the screenshots below, the expected pattern is 0xA5.

If TRACE32 is configured to expect a different pattern than the one actually used by the operating system, it will incorrectly report 100% stack usage in TASK.STacK.

To resolve this, specify the correct fill pattern with the command:

TASK.STacK.PATtern

For more details, refer to the description of this command in the General Commands Reference Guide T.

Helpful Unhelpful

Add a comment

ID-0
To prove you are a human, please tell us the text you see in the CAPTCHA image