• State Verified Answer
  • Replies 2 replies
  • Subscribers 67 subscribers
  • Views 749 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 233726
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

GDB backtrace in SDK 15

bart

When I hit the app_error_fault_handler(), gdb doesn't have a stack trace anymore: Backtrace stopped: previous frame identical to this frame (corrupt stack?)

There used to be this config HARDFAULT_HANDLER_GDB_PSP_BACKTRACE but it's gone in SDK 15. Is this now enabled by default, or has it been removed?

Using and NRF52832, SDK 15.3.0, SD 132 6.1.1. I have "DEBUG" defined.

Parents
  • +1

    Hi,

    The config is removed because "backtrace" bug is fixed in the GCC toolchain version we are recommending for this SDK release. You can use the SDK release notes to see the toolchains versions we have used for test and verification. 

    What is the fault "id" passed to the error handler? Note that you will not get a backtrace if it is a Softdevice assert (NRF_FAULT_ID_APP_MEMACC/NRF_FAULT_ID_SD_ASSERT)

Reply
  • +1

    Hi,

    The config is removed because "backtrace" bug is fixed in the GCC toolchain version we are recommending for this SDK release. You can use the SDK release notes to see the toolchains versions we have used for test and verification. 

    What is the fault "id" passed to the error handler? Note that you will not get a backtrace if it is a Softdevice assert (NRF_FAULT_ID_APP_MEMACC/NRF_FAULT_ID_SD_ASSERT)

Children
Related