PRB: WDEB386 Does Not Find Driver Symbol Files

Last reviewed: April 12, 1995
Article ID: Q73333

The information in this article applies to:

Microsoft Windows Device Driver Kit (DDK) for Windows versions 3.0 3.1

SYMPTOMS

When the Microsoft Windows 80386 debugger, WDEB386, is used to debug a modification of one of the standard drivers provided with the Microsoft Windows Device Development Kit (DDK), the debugger does not load symbolic information.

CAUSE

The module name listed in the module definition (DEF) file and the filename of the driver do not match.

RESOLUTION

For Windows to load, the module name for the standard drivers cannot change. Keep the module name and the filename the same during the debugging process for the modification. Once the file is debugged, give the file its final name.

Additional reference words: 3.00 3.10 DDKMISC
KBCategory: kbprg kbprb
KBSubcategory: TlsWdebProb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 12, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.