Correction
The variables listed in the local window do not always show the actual values in them. Sometimes they point to registers and the values in them can change after a function call. Of course I used to get all confused and started chasing perceived bugs but it turned out that the values had been stored on the stack prior to the function call but the local window hadn't been updated with appropriate reference.
Improvements
The "data window" of the debugger allows showing only one type of data window at a time. For myself I'd prefer to always have the local and watch windows displayed in different areas as default when source code debugging; with register and watch when assembly mode debugging. I'm sure others have other preferences. Memory could be optional and maybe chosen from the main menu. The memory window should allow entering an identifier instead of a hexadecimal address. If a pointer is entered it could be "live" i e when it changes the memory being displayed changes as well. When I (left) click on a source code identifier (selecting it) and then right-click I get a menu with one option being "watch." When I click watch I get an empty identifier position even though I (they way I see it) had selected one prior to clicking watch. Double-clicking on a function identifier should cause that function to be displayed.
I'm ambivalent toward the debugger automatically starting in run if a breakpoint has been defined. Perhaps there could be a "load for debugging variant"?
The code (source/assembly windows) area should "always" have the focus. If I switch to data and select a tab there and then press F10/single-step nothing happens because the data area has the focus and not the code area. To single step I need to click on the code area to move the focus back to it.
I'd prefer to be able to quit the debugger without extra clicking. Currently it requires me to acknowledge that I really want to quit it which (at least to me) is unnecessary in a vast majority of cases.
It would be great to have some quick key combinations such as alt/d+r (restart the debugger) alt/d+x to quit.
In older (non-Pellesc) debuggers it was possible to switch between source and assembly with F3, my fav IA-32 debugger from OpenWatcom has it. It also has F8 for stepping into and F7 for "run to cursor". "Run to cursor" is also available by right-clicking on a source line/assembly instruction.
