Using the Memory Browser

Debuggers are able to show a representation of the memory on the CC23xx or CC27xx. In CCS, you can index by address or by symbol name. As an example, consider the stack that was overrun in Figure 61.:

Simple Peripheral Task’s stack. Note BE watermark

GAPRole Task’s stack. Note it’s completely filled.
../_images/mem_browser_sbp_stack.png
../_images/mem_browser_gaprole_stack.png

CCS Theia also includes a memory browser, click on view into memory to enter memory browser.

../_images/ccs_theia_memory_browser.png

CCS Theia memory browser

The solution in this case would be to increase the stack size for the failing task and see what the stack peak really is. The stackPeak reported is relying on how many watermark bytes are overwritten, so it can’t know how much the overrun amounts to.

Because stacks are utilized from higher addresses towards lower addressed (upwards in the picture), stacks that overrun will tend to overwrite data at locations immediately before the stack.