Using the Memory Browser
========================

.. XXX this is only for CCS

Open the memory browser at ``View`` |RARR| ``Memory Browser`` to explore the memory on the |DEVICE|. In
:term:`CCS`, you can index by address or by symbol name. 

=================================================================  =================================================================
Basic BLE Task's stack (Note the ``A5`` watermark).        	       GAPRole Task's stack has probably overflowed as it is completely filled.
-----------------------------------------------------------------  -----------------------------------------------------------------
.. figure:: /debugging/resources/mem_browser_sbp_stack-cc23xx.png  .. figure:: /debugging/resources/mem_browser_gaprole_stack.png
=================================================================  =================================================================

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 in
:numref:`rov_task_detailed_cc2340` is relying on how many watermark bytes
are overwritten, so it can't know how much the overrun amounts to.

.. _rov_task_detailed_cc2340:
.. figure:: /debugging/resources/rov_task_detailed_cc2340.png
	:align: center

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.