OS Faulting instruction address (r15/pc): 0x000174c8

RE: OS Faulting instruction address (r15/pc): 0x000174c8

Raoul — Tue, 25 Oct 2022 13:41:11 GMT

Hi Mohamed,

I see. Unfortunately there is no support in Zephyr for generating stack traces, but it has been requested before. Until this is implemented, we will have to do with an external debugger.

Best regards,

Raoul Pathak

RE: OS Faulting instruction address (r15/pc): 0x000174c8

Learner — Fri, 21 Oct 2022 11:41:38 GMT

Hi Raoul,

Thank you for your response.

As suspected, the root cause of the crash was a stray array index getting out of range. It is fixed now.

[quote userid="117489" url="~/f/nordic-q-a/92868/os-faulting-instruction-address-r15-pc-0x000174c8/391749"]Could you run your code with a debugger, and take a look at your stack frame when it crashes? You'll see the function that was calling into libc-hooks.[/quote]

I think I did try to use the Call stack in the debugger but it did not help. SES debugger did not show the complete call stack all the way back to my application code.

My point was the error message could have been more helpful by pointing to an address in the application code.

Kind regards

Mohamed

RE: OS Faulting instruction address (r15/pc): 0x000174c8

Raoul — Thu, 20 Oct 2022 20:21:45 GMT

Hi Mohamed,

I also suspect that the problem lies with your code; it's not unlikely that it's just a C programming error, where you're writing past the bounds of an array (sorry if this sounds obvious).

Could you run your code with a debugger, and take a look at your stack frame when it crashes? You'll see the function that was calling into libc-hooks.

We don't have the capacity to help with debugging every kind of C problem, but I hope this gets you started for now.

Let me know if there's more you're wondering about!

Best regards,

Raoul Pathak

RE: OS Faulting instruction address (r15/pc): 0x000174c8

Raoul — Tue, 18 Oct 2022 09:00:47 GMT

Hi Mohamed,

I'll be looking into this soon. Sorry to let you wait.

Best regards,

Raoul Pathak