Microsoft KB Archive/92988
Article ID: 92988
Article Last Modified on 9/30/2003
- Microsoft CodeView 4.0
- Microsoft CodeView 4.01
- Microsoft CodeView 4.1
This article was previously published under Q92988
During the process of debugging an application with CodeView for Windows, it is sometimes helpful to set a breakpoint on a Windows API. The text below details the required steps to set a breakpoint:
- Run the N2D.BAT file in the BIN directory (by default, WINDEV\BIN or C700\BIN) to activate the Windows debugging kernel.
- Run the CVPACK utility on the GDI.EXE, KRNL286.EXE, KRNL386.EXE, and USER.EXE files in the WINDOWS\SYSTEM directory. Running the utility allows CVW to access the public symbols in these files.
- Start Windows and load CodeView for Windows (CVW).
- Load the application into CVW.
- In the CVW Command window, enter the following command:
where <FUNCTION_NAME> is the name of the function to break on. For example, bp GETMESSAGE.NOTE: The name of the function must be in uppercase letters because each Windows API is called using the Pascal calling convention. Also, CVW version 4.0 hangs Windows if you set a breakpoint on an API function that CVW calls. This problem is fixed in CVW version 4.01.
- When CVW halts execution, access the Calls menu. Function names in the menu are ordered from the function called least recently at the bottom of the menu to the function with the breakpoint at the top of the menu. Therefore, the second function from the top of the menu is the function that called the API function on which the breakpoint is set.
If you are using Windows for Workgroups 3.11, the debug kernel files that Visual C++ 1.5 comes with do not have symbols. Because USER, GDI, and KRNL386 have not changed since Windows 3.1, you should use the Windows 3.1 versions of these files. Visual C++ 1.0 has the Windows 3.1 debug kernel.
Additional query words: kbinf 4.00 4.10 no32bit
Keywords: kb16bitonly KB92988