How to avoid NRF faults after breakpoints?

As most developers using Nordic's SoftDevice quickly find out, halting the processor (e.g. hitting a break point) results in a fault and requires a reboot. This makes debugging on Nordic's platform infuriating. Yes, we can use RTT or constantly restart your code, but that takes lots of time and doesn't provide the visibility required to quickly diagnose issues.

Knowing that I'll get undefined issues with BLE functionality, is there anyway to temporarily disable the SoftDevice's watchdog functionality when I'm debugging other areas of my code? Perhaps by manually changing the RTC0 parameters? 

Related