Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

386SWAT debugger (Developers)

posted by Japheth Homepage, Germany (South), 28.03.2024, 06:25
(edited by Japheth on 28.03.2024, 06:38)

> Hello,
> The 386SWAT debugger seems to be able to continue tracing a real-mode (not
> V86) program that goes into protected mode, but I don't quite understand
> how to configure 386SWAT with 67h INTs, and I can't find any assembly
> language examples.
> Does anyone know how to do this?
I tested 386SWAT to run with hdpmi, but found it rather complicated - currently it just reboots if I try. May be my fault, though...

> Or do you know of another debugger that
> allows a program to change modes (RM -> PM without DPMI) while adapting to
> it? (with the segment registers which become selectors).
These are socalled "ring0" debuggers. MS wdeb386 actually works, I tried with hdpmi, but it won't do output to the screen, communicates with a serial line or a network card only. No big problem if you use a "virtualizer" like qemu or virtualbox.,,

I finally wrote my own, based on Debug/X: https://github.com/Baron-von-Riedesel/Deb386. The good thing about this debugger is that it is so small that it can remain in conventional memory ( 25 kb ) and won't have to hassle with paging things ( as long as the first MB of address space is "identity mapped" ).

Generally, such debuggers always need the help of the debuggee, that is, your program has to notify the debugger when it is appropriate to "intrude", Personally, I found the API that 386SWAT offers a bit strange, or at least not very well documented, but this applies to MS wdeb386 ( and probably deb386 ) as well.

---
MS-DOS forever!

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22049 Postings in 2034 Threads, 396 registered users, 54 users online (0 registered, 54 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum