use Turbo/Borland C/C++ in Dosbox with Inline-Assembler + Debugger. you can use visual studio with x86 inline assembler - works as long as segmented memory access or io ports access is not relevant to you, all 8/16/32bit opcodes still working. PS), or to a Windows printer on the host (it. Looking for a way to quickly test the effect of x86 instructions. If you set it up to send to the virtual printer, it can 'print' to a graphic file (.PNG. Unfortunately It seems only by doing alt pause am I able to actually cause the debugger to pause execution (and thus start debugging). The valid options in the Parallel/Dongle dialog are reallpt, printer, file and disabled. The moment I run com or exe file in Dosbox Debugger, I want it to pause execution, so I can start debugging on the FIRST opcode in the program. Then I'll probably forward port it to a recent CVS.Īnyway, I'd really like to see the search part merged, so please tell me what you think is missing / could be done better. It allows redirecting LPT1 (through LPT3) to an actual LPT port, a printer file (.prn), or to the virtual printer. I'll try to make it work this weekend, if I have time. If anyone is curious, below is a (non-working) patch with my current modifications. Quite fast, don't know if he actually implemented it. Harekiet had some idea about using custom handlers which would be The doc at Guide to the DOSBox debugger says: '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.' I added the following to my dosbox configration: log logfilec:mytestlog.txt. Handler functions to do the checks, which isn't the fastest thing to do. Really implementing this type of breakpoint requires rewriting the memory Handler functions to do the checks, which isn't the fa □ Really implementing this type of breakpoint requires rewriting the memory I was too busy testing my previous patch (read: playing games with infinite lives), so I didn't test that patch. It (note that there are only calls CheckBreakpoint(SegValue(cs),reg_eip)).ĭ'oh. About the break on memory reads: this doesn't work as you implemented
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |