Observing dynamic memory allocation and fragmentation has never been more straightforward and detecting the reasons for byte pool fragmentation has never been easier. In all thread views, a stack use indicator shows how much stack is currently in use by that thread. This information identifies threads that are using more stack space than anticipated, ideally before problems occur. Then, stack sizes can be adjusted to guard against overflow. A slight modification to a user's project enables maximum stack use checking.
Users can check stack use for a single thread or for all threads.
In either case, a window displays the peak stack usage as determined by the highest point in the stack that was changed since the thread was created. Furthermore, because this maximum stack use checking occurs on the target itself, there is no need to upload large parts of target memory simply to check maximum stack usage.