Using backtrace functionality in nrf52

RE: Using backtrace functionality in nrf52

awneil — Thu, 02 Mar 2017 11:14:09 GMT

But, as I said, it's not specific to nRF - it's general to any Cortex-M4F

RE: Using backtrace functionality in nrf52

Sigurd — Wed, 01 Mar 2017 16:14:34 GMT

I haven’t seen anyone use that backtracking library with the nRF before. In order to “unwind” and “backtrack” a common approach is to use the Call Stack and Locals Window in Keil.

RE: Using backtrace functionality in nrf52

awneil — Tue, 28 Feb 2017 18:09:43 GMT

This is actually a generic GCC/Cortex-M4 question - not specific to nRF52.

So you may well be better looking for general GCC/Cortex-M4 sources/forums...

RE: Using backtrace functionality in nrf52

Swapnil — Tue, 28 Feb 2017 17:19:20 GMT

Sorry if my question hasnt been specific enough, so I will try to clarify that...

I basically want to get the unwind-library working for the nRF52832, so that no matter where I am experiencing a runtime-error, I can easily check the printout with the specific function-name and code-line where the crash happened.

I was hoping to get some more informations regarding this issue, in case someone already tried to link an external library for the nRF52832 or might even has used some advanced error-tracing function in the nordic-SDK.

RE: Using backtrace functionality in nrf52

awneil — Tue, 21 Feb 2017 10:44:17 GMT

So which functions, exactly, are you missing?

Note that the article specifically states, "On some platforms, gcc has a built-in function..." - have you verified that your particular unnamed toolchain does, in fact, have this ... ?