debugger
debugger copied to clipboard
openMSX
Note: Not to be confounded with watchpoints (special type of breakpoint). Most debuggers have a watch feature (usually a dockable or window), where you can add variables to be watched....
I compiled the latest code from github (both openMSX and the debugger) and when I for example place a break point on 0x0100 (DOS) and start with a dos disk...
 I get this assert when I'm running a rom image in a rom type that uses a mapper chip that can't address this much in a real chip (in...
There seems to be a much simpler solution for issue #21: we reload `DisasmViewer` code window when we enter break state. A bit of a waste of resources, but the...
**Reported by sd-snatcher on 2009-03-07 14:25 UTC** Sometimes openMSX-debugger stays showing older data, then I have to close it and open again, to force it to reload everything. It would...
The "Use Palette Registers" checkbox of the Bitmapped VRAM View doesn't work anymore. If I deselect it, the image is still shown with the current color palette instead of the...
The debugger has problems to run with the NEOS MA-20. Maybe it's hardcoded to the default I/O ports? For example, with the MA-20 connected: - The Bitmapped VRAM View "Current...
The debugger lacks refreshing possibilities, when executing Z80 mnemonics / opcodes , debugging can be done correctly when you know instantly the values generated by the client. All of the...
Delete all January 27th assets in the nightly release (in https://github.com/openMSX/debugger/releases/tag/nightly) to update the last release date when github-actions runs successfully. This happens because the name of the release binaries...
In the newer versions of this debugger, the code view is too small and it cannot be resized either. System: OS: Windows 10 Pro Emulator: OpenMSX 18.0 Debugger: nightly 2022-04-06
