TMS570LC4357: CCS Debugger issue - can't see call stack and i can't use Step Into debug function (GCC Linaro compiler)

Radek Hyvnar

Hello,

I built a project using:
- CCS 10.4.0 (Windows)
- GNU v7.2.1p1 (Linaro)
- Target arch: armv7-r
- Tuned for: cortex-r5

Build was successful and i've loaded the program with the following message:

CortexR5: Symbol Manager: the object file contains invalid call frame information at .debug_frame 0x0; the rest of call frame information will be skipped. Callstack may not be unwound properly.

I can't see call stack and i can't use Step Into debug function (it just skips over any function calls) the only way to step into function is by using Assembly Step Into. Everything else seems to work fine.
I've tried to change DWARF version and other debugging flags as well as optimization levels (none, -Og).

Please help,

Radek

over 3 years ago

0 Kowshik Gudimetla over 3 years ago

TI__Genius 15435 points

Hi Radek Hyvnar,

I've seen you mentioned the CCS version as 10.4.0 which is a much order version. Can you please try downloading the latest CCS version https://www.ti.com/tool/download/CCSTUDIO and see if the same error still exists please?

Thanks,
G Kowshik

0 Radek Hyvnar over 3 years ago in reply to Kowshik Gudimetla

Prodigy 110 points

Upgrading to CCS 12 fixed some issues but call stack still doesn't work properly (testing with optimizations disabled, gdwarf 4).

Call stack disappears after I step into function. When I stepped through the code using disassembly, I’ve found out that at the very start of function, call stack displays current function and the calling function. After instruction “000f1ba8: E24DD020 sub” calling function disappears from call stack. This goes for any function.

Disassembly of function:
foo()
000f1ba0: E92D4800 push {r11, r14}
000f1ba4: E28DB004 add r11, r13, #4
000f1ba8: E24DD020 sub r13, r13, #0x20
000f1bac: E50B0020 str r0, [r11, #-0x20]
Next line of code…