https://devzone.nordicsemi.com/f/nordic-q-a/81606/hardfault-reading-nrf-log-from-flash-backendWith SDK15.3 (it appears the issue exists in 17.1 as well), we are using the flash backend. To read the logs, we are doing the equivalent of flashlog_read_cmd(). This eventually calls nrf_log_color_id_get() and nrf_log_module_name_get(). I see that nrf_log_module_name_geten-USTelligent Community 13Thu, 11 Nov 2021 17:52:08 GMThttps://devzone.nordicsemi.com/thread/338648?ContentTypeID=1Thu, 11 Nov 2021 17:52:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:37f54983-6341-49a2-b3a0-1f3fc4bc3365BretH<p>Actually upon further review, the root cause of the hardfault is likely due to corruption in the&nbsp;<span>p_header</span><span>-&gt;</span><span>base</span><span>.</span><span>std</span><span>.</span><span>addr from&nbsp;</span>nrf_log_backend_flash_next_entry_get(). If a bad address is passed to&nbsp;nrf_log_std_entry_process(), there definitely could be potential for trouble.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/338561?ContentTypeID=1Thu, 11 Nov 2021 12:28:50 GMT137ad170-7792-4731-bb38-c0d22fbe4515:20761e8c-e96a-410a-9278-d925f226f64fSimonr<p>Hi</p> <p>Thank you for reporting this. I have created an internal ticket on this and our developers will review this issue. If you&#39;d like I can keep you updated on our progress. Glad to hear you&#39;re able to fix this on your end.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>