DOSBox debugger

Topic actions

Reply 120 of 121, by siddhartha

User metadata
Rank Newbie

Since I've been using DOSBox for development a lot lately , I've created an updated patch that adds a few more debugger commands and some fixes.

  • The Debugger window can no longer be resized on Windows 10, which would mess up the formatting. The window can no longer be maximized either since it's a static size.
  • When closing the debugger, DOSBox will exit with a status code 0, which works better if run from a batch file.
  • New debugger commands:
    • DA: Will disassemble n bytes from segment:offset to a text file (defaulting to DISASM.TXT)
    • BPSAVE: Will save the current breakpoint list to BPLIST.TXT
    • EXEC: Will execute debugger commands from the specified file (comments can be made using a semicolon ";")
  • An autoexec file can be specified with autoexec= in the debug section of dosbox.conf. Just like the command file above, comments can be made using a semicolon.

The attached dosbox.exe is built against SVN 4454.


Reply 121 of 121, by dr_st

User metadata
Rank l33t

Just an idea I had - for capturing interrupt 31h (simulate real-mode breakpoint), it would be useful to extend BPINT to trigger not only on AH/AL but also on BL - since this is where the real-mode interrupt number is stored, when 31h is called.

https://cloakedthargoid.wordpress.com/ - Random content on hardware, software, games and toys