linear memory version of debugger command SM?

[leslietoo]

Question

There's a SM command built into the debugger:
SM [bytes in hex] Set memory at : to byte values given

SM works under real mode apps/games, but it seems not to work under 32bit protected apps/games like in windows98, I tried SM but nothing changed. So maybe we need a linear memory version SM for protected mode?

Have you checked that no similar question(s) exist?

• I have searched and didn't find any similar question.

Code of Conduct & Contributing Guidelines

• I agree to follow the code of conduct and the contributing guidelines.

[joncampbell123]

"SM" as inherited from DOSBox SVN expects a 16-bit segment:offset (though offset can be 32-bit). Unless there's any reason not to, it should support protected mode segment:offset as well.

How does "SML" sound for the linear (virtual) flat memory model version?

"SMP" for physical memory?

Understand that the write may fail in protected mode if the debugger attempts a write but the page is marked not present by the guest OS. I'd rather not accidentally cause the debugger to resume execution just for a page fault so it needs to fail that way. However perhaps there should be a debugger command that explicitly touches a guest page with the expectation of resuming execution for guest page faults.

[joncampbell123]

By the way DOSBox-X changes to the debugger should allow you to use the register names in the SM command instead of typing in the hex value manually.

For example:

SM DS:ESI 40 20 80

[joncampbell123]

Latest commit adds a "SMV" command, enjoy!