Running function stack trace

[outspace]

Hi,Master:

Question：

When the finished product cannot be debugged with jlink, I want to save and trace the function stack information through the firmware. When there are some accidental exceptions, I need to use the function stack to more delicately locate the problem.

My way of implementation:

foo_1 ()
{
    FUNC_TRACK_PUSH (foo_1);    // Push the function address into the stack structure
 
    ...// dosome thing
 
    FUNC_TRACK_POP (foo_1);     // Pop this function address from the stack structure
}
 
foo_2 ()
{
    FUNC_TRACK_PUSH (foo_2);    
 
    ...// dosome thing
 
    FUNC_TRACK_POP (foo_2);     
}
 
.
.
.
 
foo_x ()
{
    FUNC_TRACK_PUSH (foo_x);    
 
    ...// dosome thing
 
    FUNC_TRACK_POP (foo_x);     
}

When an exception occurs during use, the current function stack call information can be obtained through the stack structure to assist in analysis.

Disadvantages:

This FUNC_TRACK_PUSH / FUNC_TRACK_POP macro must be added to the entrance and exit of all functions to record the current function stack call, which is complicated and coupled. Is there a more elegant way to achieve it?

Forgive me for poor English. Thank you!

regards

[Kenneth]

I think this can be done simpler. When the processor takes an exception, the processor pushes information onto the current stack. See here:

https://developer.arm.com/documentation/dui0552/a/the-cortex-m3-processor/exception-model/exception-entry-and-return

Thereby I believe you can get the information you want from the call stack. Typically in the nRF5 SDK you can for instance catch exceptions (hardfaults) by including (one of the files are compiler specific):

$(SDK_ROOT)/components/libraries/hardfault/hardfault_implementation.c 
$(SDK_ROOT)/components/libraries/hardfault/nrf52/handler/hardfault_handler_gcc.c 

After adding the above files and setting HARDFAULT_HANDLER_ENABLED 1 in sdk_config.h, you should be able to catch the hardfaults in HardFault_c_handler() and can process these as you like. 

[outspace]

Hi,Kenneth

Sorry to reply you so late, thank you for your guidance

Because sometimes, for example, some dynamic memory overflows cause occasional program exceptions, I want to use this idea to determine and narrow the scope of the problem, I want to see the same context as the call stack window in the IDE, and further provide me with some ideas

Thank you very much.