I have a set of source which is a driver written for DOS.
The corresponding application has to launch this driver before running.
I'd like to see how this driver works. What are the general steps of debugging this software?
if I run the debugger against this application, will it switch to the driver when needed?
Last edited by lucky6969b; October 1st, 2011 at 03:54 AM.
I can't remember if it was possible to step into a DOS int call but it might have been so. Anyway, the first thing you need is to get yourself a DOS compiler/linker/debugger. Is the source C or assembly? Hopefully the code was written using one of Borland's Turbo suites since some are now freeware see http://en.wikipedia.org/wiki/Borland_Turbo_C
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan