Click above to get retro games delivered to your door ever month!

The debugger automatically detects all DLLs that your application references
when it loads the application.  When your program loads a DLL dynamically,
the debugger detects this as well.  If you have created your DLL with
debugging information, you can debug it just as if it were part of your
application.  Even if it does not have debugging information, the debugger
will process system information to make the DLL entry point names visible.
 There are a few limitations:

 1. You cannot debug your DLL initialization code.  This is the first
    routine that the operating system runs when it loads the DLL.  This is
    not normally a problem, since most DLLs do not do much in the way of
    initialization.

 2. When a DLL is loaded dynamically, its debugging information may not be
    available immediately.  Try tracing a few instructions and it will
    appear.

 3. If you restart an application, you will lose any break points that you
    had set in dynamically loaded DLLs.  You need to trace back over the
    call to LoadModule or DOSLoadModule and re-set these break points.