I would love to see trace to file and trace to screen options in all your emulators (they seem to share a common layout). I'd say trace to window could display that last 2000 or so instructions executed before a breakpoint, and the file could support everything until the breakpoint. What I would like to see in such a file is below:
Also; if possible, could you have it classify loop executions into single entries with a numeric representation of the execution count above (see MESS trace logs)? You have a very rich debugger outside of these missing features (this is in my opinion one of the basic features a debugger should contain), and they are sorely missed at the moment by hacking communities (especially for NDS).
The last feature would be a way to search the memory in most if not all your emulators. Currently we have to attach an external application that will resolve memory addresses within your emulator for cheat use, or use another emulator entirely (which results in the loss of the debugger). It would be nice to have such basic features built into a future release if you have time to implement it. Keep up the great work!
Code:
Address Bytes Instruction Literal (optional register values)
The last feature would be a way to search the memory in most if not all your emulators. Currently we have to attach an external application that will resolve memory addresses within your emulator for cheat use, or use another emulator entirely (which results in the loss of the debugger). It would be nice to have such basic features built into a future release if you have time to implement it. Keep up the great work!