When a piece of code is compiled with C some extraordinary things happen... I suspected that C was being used.
There is a COF / CDG /OMF file created... This file produces all debug information.... BUT!!! Your optimizer steps in and all hell breaks loose..
If in a C file you have several statements that loosely do the same thing... Only one line will actually get compiled.. So when debugging try turning off the optimizer.. HEED all warnings, they can give you a clue... Unfortunately I don't use Renesas Software any more... I used it extensively when I was primarily using Philips XA series chips. It was called RIDE then, but no more.. Possibly 10 years since so the software will be very different!! They don't even seem to support Philips anymore...
Looking at the software... It seems as they use CDB debugging.. However! they also have adopted the Eclipse IDE and each compiler is an addon and so is the debugger..
You may be better off at the e2 studio forums... Or at least the compiler forum... Which device are you using???
I used to be able to hover over local variable to see it's value. Now, I cannot hover over local variables in the debugger. However, in eclipse IDE I can hover over local variables and see information. I think something is not setup correctly in my debugger. Do I need to do something with the Indexer ? What is it ? How to use it ?
In my e2studio I cannot put breakpoints anywhere but my application runs fine.
From main menu, I open Window - Show View - Disassembly
When Disassembly window opens, e2 studio stops responding.