app_error_fault_handler missing p_file_name and line_num

[michaelhobo]

I am trying to debug an app error in my code. I have an app_error_fault_handler that starts like this:

extern "C" void app_error_fault_handler(uint32_t id, uint32_t pc,
                                        uint32_t info) {
  if (id == NRF_FAULT_ID_SDK_ERROR) {
    error_info_t* err_info = (error_info_t*)info;
    LOG_E("Fatal Error in file %s, line %d", (const char*)err_info->p_file_name,
          err_info->line_num);
    switch (err_info->err_code) {
      case NRF_ERROR_SVC_HANDLER_MISSING:
        LOG_E("Error Code: NRF_ERROR_SVC_HANDLER_MISSING");
        break;

But, the "Fatal Error in file..." line doesn't show the file name and line number. I use this fault handler on other systems, and I've seen the file name and line number before.

The err_code in the error_info_t struct is NRF_ERROR_INVALID_STATE though (which is the value 8), so it doesn't seem like the error_info_t is empty.

Why aren't the file name and line num fields populated? I feel like I might be missing something simple.

Here's the output:

00> <error> app: Fatal Error in file , line 0
00> <error> app: Error Code: NRF_ERROR_INVALID_STATE

[michaelhobo]

I put an APP_ERROR_CHECK(NRF_ERROR_BUSY); right after initializing logging, and same issue occurs, with NRF_ERROR_BUSY instead. So I'm pretty sure it's some config issue (sdk_config.h? gcc flags?)

[Sigurd]

Try adding DEBUG in your preprocessor defines, both as C flag and assembler flag.

CFLAGS += -DDEBUG

ASMFLAGS += -DDEBUG

If that does not help, try looking at the call stack with Ozone (use the generated .elf file with Ozone) to see where the error originated from.

[michaelhobo]

Adding -DDEBUG solved it for me! Sorry for the late reply, I was focused on something else.