Debugging a driver (non-device driver)
CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums
Results 1 to 4 of 4

Thread: Debugging a driver (non-device driver)

  1. #1
    Join Date
    Dec 2010

    Debugging a driver (non-device driver)

    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 04:54 AM.

  2. #2
    Join Date
    Jul 2002

    Re: Debugging a driver (non-device driver)

    Driver for DOS ??? Are you sure? Possibly you need first to understand what is target OS for this program.

  3. #3
    Join Date
    Dec 2010

    Re: Debugging a driver (non-device driver)

    Maybe it's just a TSR
    Thanks Alex

  4. #4
    Join Date
    Oct 2006

    Re: Debugging a driver (non-device driver)

    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
    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

    To enhance your chance's of getting an answer be sure to read
    and before posting

    Refresh your memory on formatting tags here

    Get your free MS compiler here

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Windows Mobile Development Center

Click Here to Expand Forum to Full Width

This is a survey!

HTML5 Development Center