search

kierenj / 0x10c-DevKit

0x10c DevKit
http://0x10c-devkit.com/
39 stars 4 forks source link

move memory view in the bottom tabbed window and refresh it #99

Open kirinyaga opened 12 years ago

kirinyaga commented 12 years ago

And more importantly make the memory view refresh after each step (easier if it's smaller ;)), so we can manage a buffer while the code is going through it.

kierenj commented 12 years ago

With this one in particular: you are aware there is already a Memory view, and would like it simply moved to the bottom tab group? (This is possible via drag-and-drop already, but is not the default). It does already refresh after each step, by the way, but not each instruction while it's running. Did you mean updating 'live' during running?

kierenj commented 12 years ago

If you're looking at highlighting changed memory/registers, could you open a new issue. Just looking for more information about what kirinyaga had in mind in this one, thanks :)

kirinyaga commented 12 years ago

I didn't realize you could move the windows ... :confused

Highlighting could be nice, yes, but indeed I was speaking of a live update. In slow mode, you could see a loop filling a buffer or so. As an alternative, having a "step over" would do it.

My problem is I always forget to set a breakpoint, hit run, then remove the breakpoint to go over a long loop I'm not interested in unless something special happens. Then I end up deep buried in my code and has to find back the portion I wanted to watch. I know a "step over" is difficult to do in assembler (only work with JSR), thus the idea to let the CPU run in slow motion and watch the memory.