PRB: API Names Don't Appear in Mixed-Source/Asm Mode

 Last reviewed: July 22, 1997
Article ID: Q117683
1.50 WINDOWS kbtool kbprb

The information in this article applies to:

  • The Visual Workbench Integrated Debugger included with: Microsoft Visual C++ for Windows, version 1.5

SYMPTOMS

With Visual C++ 1.0, when you run N2D.BAT to use the debug version of Windows, you are able to see the Windows API names in the debugger window while stepping through your code in Mixed Source/Assembly mode. For example, if you have a call to DrawText() in your code, in either CodeView or the Workbench debugger, you will see the line: 

   CALL DRAWTEXT (0767:1ECF)
However, when using the debug kernel that comes with Visual C++ 1.5, you will not see the API name; you will see: 

   CALL 0767:1ECF

CAUSE

The difference is that Visual C++ version 1.0 debug kernel modules contain CodeView debugging information, while the Visual C++ 1.5 debug kernel modules do not contain CodeView information.

RESOLUTION

If it is important for you to be able to see API names in the debugger, you may use the debug kernel, which is included with Visual C++, version 1.0, and Visual C++, version 1.5.

MORE INFORMATION

Visual C++, version 1.0, contains the debug kernel for Windows version 3.1, while Visual C++ 1.5 contains the debug kernel for Windows for Workgroups version 3.11. You may use the Windows version 3.1 debug kernel with Windows for Workgroups without problems.

Additional reference words: 1.50
KBCategory: kbtool kbprb
KBSubcategory: WBDebug
Keywords : kb16bitonly

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: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.