I've been using E2 studio from version 7.5 through 7.8, and in none of them does the debug "step over" function actually work. It ALWAYS steps INTO the instruction. This is maddening in trying to debug code of any length.
My question is: WHEN will this be FIXED FINALLY?
I have been reading of others who have this issue, from as far back as V7.5 / V7.6. Before that, this function might have worked.
Having this severe handicap makes debugging of code very, very lengthy and very incomplete and virtually impossible to do. I would have thought that Renesas would have figured this out by now after, how many?, releases, and yet...not hardly.
I am working currently with V7.8 and i am running on Windows 7 SP1. Yes, i know that Win 7 is only officially supported up to V7.6 (which is also broken vis-avis debug "step over"), but i would wager that there are still many, many developers out there who are still using Win 7 and have not moved onto Win 10 and probably won't because of other development software that will only run on Win 7 or 8.
When (???) will Renesas finally issue an update to fix the debug "step over" issue? AND will they fix it for people still on Win 7?
Hi, thank you for your input. I already have compiler optimization off and I've always had it off. The step-over function has never worked for me, always stepping into the instruction. I'm curious what other settings you have that allow your debug code to step over rather than into the instruction. By the way, just to be clear, i can step from instruction to instruction (ie: into), but never step over.
Thanks AE, it was a good suggestion, but unfortunately it doesn't work with step-over. It was definitely worth a try. Again, thanks for your help. Do you have any other thoughts on this?