CCS/PROCESSOR-SDK-AM437X: Debug window does not match executable code

Samuel Nesbitt

Tool/software: Code Composer Studio

When single stepping it will randomly jump to blank lines, unable to set breakpoints, unable to watch variables.
It looks like the debug window is not displaying the correct source code.

Also, I get the following error when trying to "run to line":

Run to Line failed.
Failed executing run to line
Failed executing run to line
org.eclipse.core.runtime.CoreException: Failed executing operation on line 284 in file GPIO_v1.c. Make sure the selected line number is an executable line.

Any suggestions?

over 8 years ago

0 desouza over 8 years ago

TI__Guru**** 171299 points

Hi,

This is a common behaviour when trying to debug optimized code - basically the optimizer rearranges lines of code and inlines functions that can confuse the debugger when interpreting the executable symbols.

If that seems to be your case, please check section 5 of the article below that talks about tips to debug optimized code.

processors.wiki.ti.com/.../Debug_versus_Optimization_Tradeoff

Hope this helps,
Rafael

Code Composer Studio™︎

Code Composer Studio forum

CCS/PROCESSOR-SDK-AM437X: Debug window does not match executable code