DOSBox debugger
Posted: Mon Jun 10, 2019 6:48 pm
Hello, fellow DFU developers
During the last months, I've gathered some experience at reverse engineering classic mechanics. However, my current method of doing it is essentially static. Even if I managed to understand some very useful functions and translate them from decompiled C code to DFU C# engine (see my recent PR related to NPC greetings), the main problem I have is I can't manage to use DOSBox debugger properly.
I'm able to locate the exact instruction where I want DOSBox to stop and put a breakpoint there. But then, either DOSBox never breaks (even if it goes through the code) or if it does, I'm unable to step over/through the following instructions using F10/F11. It's quite frustrating and the only solution I came into is to set breakpoints on a dozen function instructions, hoping DOSBox will eventually break into one of them. And then, if it does, I can only hope current CPU registers will give me enough information.
I'm pretty sure I'm not doing things right but even after looking for information on the internet, I can't understand why DOSBox debugger is behaving like it does with DF. So, did some of you manage to use it successfully?
To be honest, I really missed good old SoftICE. I used it like 20 years ago and never found any other debugger as powerful as this one was. Back in the days, I remember finding and tweaking the "loiter a while" 3 hours time limit in less than 30 minutes...
During the last months, I've gathered some experience at reverse engineering classic mechanics. However, my current method of doing it is essentially static. Even if I managed to understand some very useful functions and translate them from decompiled C code to DFU C# engine (see my recent PR related to NPC greetings), the main problem I have is I can't manage to use DOSBox debugger properly.
I'm able to locate the exact instruction where I want DOSBox to stop and put a breakpoint there. But then, either DOSBox never breaks (even if it goes through the code) or if it does, I'm unable to step over/through the following instructions using F10/F11. It's quite frustrating and the only solution I came into is to set breakpoints on a dozen function instructions, hoping DOSBox will eventually break into one of them. And then, if it does, I can only hope current CPU registers will give me enough information.
I'm pretty sure I'm not doing things right but even after looking for information on the internet, I can't understand why DOSBox debugger is behaving like it does with DF. So, did some of you manage to use it successfully?
To be honest, I really missed good old SoftICE. I used it like 20 years ago and never found any other debugger as powerful as this one was. Back in the days, I remember finding and tweaking the "loiter a while" 3 hours time limit in less than 30 minutes...