Quantcast
Channel: Tools
Viewing all articles
Browse latest Browse all 91752

Forum Post: RE: "Collapsing" register and memory browsers

$
0
0

Hi Rafael,

this was an almost perfect answer. I guess we can make it completely perfect.

First, just or the sake of completeness: I am not 100% sure what you mean by So far I always stopped debugging when I assembled new sources because I was prompted to do that. This switched to the CCS Edit perspective. I started assembly with the Debug button with the greenish bug. That reopened the Debug perspective. But in the Register Browser window only the register overview was visible, not the previously unfolded detail view with e.g. PC, SP, SR, R3 etc. visible. Also the Memory Browser Window was grey and I needed to activate Go.

Anyway, I wasn't aware that I can ignore the message "You are required to terminate existing debug session..." and used to confirm it with Yes.

Now I know that I simply needed to confirm the next message box  "A file that you are debugging (...) has been modified. Do you want to reload this file?", remember my decision, and the new code is started without terminating the debugger.

Once the debugger is launched and you are debugging code, you can simply switch back to the CCS Edit perspective

It seems I don't even need to toggle between these perspectives. Did I miss something?

when you launch the debugger by clicking on the green bug button

I guess you mean the Debug button with the greenish bug? Or is there another function that I missed?

Final question: Is there a means to avoid to be forced to answer No to "You are required to terminate existing debug session..."? This would be the final littleness for the perfect answer and allow a simple one-click assemble-and-relaunch action.

Up to now, thanks a lot!!!


Best regards, Uwe


Viewing all articles
Browse latest Browse all 91752

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>