Strange Behavior using arm-none-eabi-gdb

I'm new to gdb so I would really appreciate any guidance. My target is the K82f and I am calling Openocd and gdb from the command line.

Compiler: ArmClang/Armlink
Debug Info: -gdwarf-4

The Issue:
Gdb doesn't print the current source-line when stepping nor does it print the source-line when using the frame command. There are also these double arrows that may be TAB characters that are being rendered to the console.

Could this be caused Openocd/gdbserver?

What resources should I look at for this?

Are there compatibility issues with Armlink generated .axf and gdb?

Parents Reply Children
No data
More questions in this forum