Hello Bob, > Sorry to intrude on this technical discussion, but an open source PM debugger > such as 386SWAT can trivially be set to detect reads and/or writes to any > location such as 40:96. Set it to detect writes, and it pops up exactly when > they happen.
nothing to be sorry about :) Thanks for pointing that out to me. As 386SWAT seems to be a mighty tool, it will take some time for me to learn how to use it (until now I mainly used the Watcom Debugger for C code and a DEBUG derivative [1] for assembly). > I realize that you might not consider 386SWAT to be an acceptable addition to > FreeDOS, but that doesn't mean you can't use it solely for debugging > situations such as this. Is it the 386SWAT provided at [2]? As it seems to be under GPL3, I do not see any reason why it should not be an acceptable addition. I think the distribution would benefit from adding this tool. I found one mention of 386SWAT in our mailing list. Jerome Shidel wrote on 21th february 2023: > Test running some of the 386MAX executables, I saw they all still display the > old license information. That should be updated to reflect it has been > released as GPLv3 and re-compiled. The same is most likely the case with > 386SWAT. But, I have not verified that. 386MAX already seems to be in our distribution [3]. But it does not include the 386SWAT binary. So maybe it is worth providing a separate package for it? Original 386SWAT binary can be downloaded from [4]. [1]: https://pushbx.org/ecm/web/#projects-ldebug [2]: https://github.com/sudleyplace/386SWAT [3]: https://gitlab.com/FreeDOS/drivers/386max [4]: https://www.sudleyplace.com/download.htm Bernd _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
