Explanation required for known issue related to logging in nrf connect sdk 1.3.2

Question

With reference to the following known issue: NCSIDB-114: Default logging causes for nrf connect sdk 1.3.2. Is there any further documentation regarding the workaround mentioned: " Do not enable logging and add a breakpoint in the fault handling, or try a different logging backend ". 
 What exactyl does "try a different logging backend"? For which logging backends does this cause a problem? I am working with RTT backend to see debug logs. 
 I am trying to figure out if this is relavent to another ticket I created: application crashes when debug log enabled using CONFIG_NET_LOG

user111520 · Answer

Enabling default logging in the Secure Partition Manager sample makes it crash if the sample logs any data after the application has booted (for example, during a SecureFault, or in a secure service). At that point, RTC1 and UARTE0 are non-secure. 
 
 Sounds like the issue affects logging on UART, which means that RTT is "a different logging backend", so this issue should not affect you. 
 Best regards, 
 Einar