Interrupt

Faster debugging with watchpoints | Interrupt

One of the most challenging types of issues to debug is memory corruption! Memory corruption can be caused for a variety of reasons including when data is used after it has been freed, a read or write goes past the end of a buffer, thread safety constructs are missing, or a linker script is misconfigured. By the time the system finally faults or encounters an error, the original operation which spiraled the system into the bad state is often lost!


This is a companion discussion topic for the original entry at https://interrupt.memfault.com/blog/cortex-m-watchpoints