RTEMS 4.8.0 On-Line Library

Stack Bounds Checker When a Task Overflows the Stack

RTEMS C User's Guide

25.3.4: When a Task Overflows the Stack

When the stack bounds checker determines that a stack overflow has occurred, it will attempt to print a message using printk identifying the task and then shut the system down. If the stack overflow has caused corruption, then it is possible that the message can not be printed.

The following is an example of the output generated:

BLOWN STACK!!! Offending task(0x3eb360): id=0x08010002; name=0x54413120
  stack covers range 0x003e5750 - 0x003e7b57 (9224 bytes)
  Damaged pattern begins at 0x003e5758 and is 128 bytes long

The above includes the task id and a pointer to the task control block as well as enough information so one can look at the task's stack and see what was happening.

RTEMS C User's Guide