You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can get the debugger to launch and get to a entrypoint, but then as I step through each instruction, the debug view switches to lines prefixed with debug001:XXX and then subsequent steps are stuck within debug001 lines until the debug session ends. I also get this interesting warning on start-up.
The text was updated successfully, but these errors were encountered:
I made some updates. It may do better now. Please keep in mind that it can only emulate code that is present in your database. In particular most int 0x21 will cause problems. I'd be interested in any feedback that you have.
Hi @cseagle thank you I will give it a try later this week. In the end I used the old MS CV DOS debugger. It was painfully slow, but I've got my app mostly decompiled now. Note I started out with the DOSBOX debugger, but that was crashing many times on certain instructions!
I'm having trouble debugging a 16bit DOS EXE
I can get the debugger to launch and get to a entrypoint, but then as I step through each instruction, the debug view switches to lines prefixed with debug001:XXX and then subsequent steps are stuck within debug001 lines until the debug session ends. I also get this interesting warning on start-up.
The text was updated successfully, but these errors were encountered: