Compiler/TM4C129XNCZAD: Reading the call stack in the code

Shlomo Hecht

Part Number: TM4C129XNCZAD
Other Parts Discussed in Thread: SEGGER

Tool/software: TI C/C++ Compiler

Hi. my Errhook now calls Error_getSite() to get the file and line of the last call before the fail. but this line is usually not usefull - already deep in the OS.

I am looking for a way to get the previous lines in the call stack. clearly the information is available somewhere- for the debugger.

Thanks

Shlomo

over 5 years ago

0 cb1_mobile over 5 years ago

Guru 117855 points

Shlomo Hecht said:
Clearly the information is available somewhere - for the debugger.

Might this be (even) better provided by, 'Code Trace' capability - which (usually) proves beyond the capability of 'vanilla' (basic) debuggers.

You may wish to visit 'Segger's web site' - their 'J-Trace' may prove of high interest...

0 Ralph Jacobi over 5 years ago

TI__Guru*** 135355 points

Hello Shlomo,

You should be able to use the View Disassembly option to see the hierarchy of function calls - provided you are using CCS.

0 Shlomo Hecht over 5 years ago in reply to Ralph Jacobi

Intellectual 330 points

Maybe I was not clear enough. I am looking for a way to read (and store) the call trace from *within the code*, not with a debugger.

0 Chester Gillon over 5 years ago in reply to Shlomo Hecht

Guru 92251 points

I haven't seen any support in TI-RTOS or SYS-BIOS to read the call trace from within the code.

From a quick search did find the code at ARM Stack Unwinding but haven't tried that sample code yet.

Arm-based microcontrollers

Arm-based microcontrollers forum

Compiler/TM4C129XNCZAD: Reading the call stack in the code