A couple of weeks back I was working through a code composer issue where multiple break points were being generated for a single (C) source line This was subsequently resolved by migrating the build optimization level from -O0 (None) to -Og (Optimize for debugging).
I've just noticed that with some builds (not all, and haven't figured out the pattern yet), local variables are now not being displayed in the Variables window, and cannot even be added in the Expression window. This is all with the build optimization at -Og. Moving the optimization back to -O0, makes these visible again.
So I'm guessing that -Og is somehow suppressing symbol information for local variables. Why it would do this for a optimization model that is supposedly for supporting debug, I haven't a clue. It doesn't feel logical, so I'm suspecting something else is at play.
CCS is V10.4, toolchain is GCC