INTT works like INT but will return into debug mode right away, so you can analyse the interrupt handler.It will return after the interrupt returns (unless a breakpoint activates before). C / D : jumps the code or data view to the given location.BPDEL / * deletes one breakpoint (use BPLIST to get the number) or all.BPLIST outputs a list of all currently set breakpoints.Enter an asterisk (*) for if DOSBOX should break regardless of the value of AH. BPINT sets a breakpoint that activates when the program calls the given interrupt and AH has the given value.BP : sets a breakpoint at the given position.See next chapter for detailsĬommands are executing by hitting ENTER, entering the command in the command line that appears and confirming them by another ENTER. ENTER opens a command line below the code view (a -> appears).F10 steps over the next instruction (does not trace into calls).F9 sets or removes a breakpoint at the current code view position (the line will be marked red).DOSBOX can display next to commands that deal with memory the current value of the referenced location.D, E, S, X, B moves the data view to DS:SI, ES:DI, SS:SP, DS:DX or ES:BX respectively.R and F scrolls the data view up and down.Obviously DOSBOX doesn't know where multi-byte opcodes starts so moving up may screw up the disassembler until you find the actual beginning of a command. Cursor Up will move the code view one byte up.Cursor Down moves the code view one command down.H displays a reference of all keys and commands offered by the debugger. The following keys can be used while in debugger mode: If you want these debug messages to be saved into a textfile for later analysis, use the logfile entry in the log section of the config file. It shows the current value of the CPU registers (those who changed since the last update are colored), a part of the memory content as hex data and assembler code (the command that will be executed next is marked green) and various debug messages. DOSBOX has a separate debugger window that should have opened when DOSBOX started. To pause the execution and start up the debugger, just press the Alt-Pause-key. So if you want to use breakpoints, heavydebug is the better choice. Unlike the debug version, heavydebug does not use INT 3 to realize breakpoints.Heavylog: Dumps the last (currently 20000) executed commands to a textfile when a program crashes or interrupt CD is called.CPU log that outputs the next n commands executed by the CPU to a textfile.Memory breakpoints that activates when the value of a memory location is changed. The heavy debug version will give you the following extra features: If you want a heavydebug version, edit config.h after running configure and define C_HEAVY_DEBUG. In order to get a debug version, add the switch "-enable-debug" when calling configure: Compiling the debug / heavydebug version of DOSBOX You should just save you the trouble and not try to use the debugger.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |