Skip to main content

When debugging optimized code, single stepping is jumping back and forth in an unexpected order. - Knowledgebase / TRACE32 PowerView - Lauterbach Support

When debugging optimized code, single stepping is jumping back and forth in an unexpected order.

When stepping through optimized code, TRACE32 sometimes seems not to execute the step correctly, the program counter (PC) remains at the same source code line for multiple steps or is jumping back and forth in an unexpected order. The List window usually shows a drill-down box (a  +  sign) next to some line numbers.

This is a result of the compiler settings and compiler output. As a workaround, summarize adjacent blocks of assembler code when loading an application, e.g. with 

Data.LOAD.Elf my_application.elf /SingleLineAdjacent 

Please refer also to the video Debugging Optimized Code in TRACE32

Helpful Unhelpful

Add a comment

ID-0
To prove you are a human, please tell us the text you see in the CAPTCHA image