The information in this article applies to:
SUMMARY
CodeView for Windows (CVW) can view symbolic information in Windows's
core code and can set breakpoints inside Windows functions when the
debugging versions of USER.EXE, GDI.EXE, KRNL286.EXE, and KRNL386.EXE
are installed in your development environment.
MORE INFORMATION
For CVW to access Windows symbols, USER.EXE, GDI.EXE, and either
KRNL286.EXE or KRNL386.EXE must be loaded into CVW as dynamic-link
libraries (DLLs). This can be done with the /L command-line switch or
in response to the DLL prompt when CVW starts.
When the symbols are loaded, you can set breakpoints at a particular function name, disassemble a Windows function, list all the modules, and list all functions contained in those modules. Note that whenever you use the name of a Windows function that is defined with the PASCAL calling convention, you must type the name in uppercase letters. When the name of a Windows function begins with a capital letter, such as the GetDC function, the function is defined with the PASCAL calling convention. The name of a function defined with the C calling convention, such as the wsprintf function, begins with a lowercase letter. To set a breakpoint, use the BP command or the Watch menu, and specify the symbol for the function name. To disassemble Windows code, use the command
where <module> is the name of the module you want to disassemble and
<function name> is the name of a function in that module. The
character "!" after the module name is required. Disassembly takes
place in the source window.
In CVW, the X* command lists all available modules. This command lists the names of all modules in the application and in any loaded DLLs. Once a module name is known, the following command lists all the functions within that module:
ExampleKRNL386.EXE has a module named LDDEBUG. To list the functions in this module, enter the following in the command window:
The output window displays many addresses with no symbols, but the
listing includes OUTPUTDEBUGSTRING. This shows that the
OutputDebugString function is implemented in the LDDEBUG module.
If [<module>!] is not specified, the functions in the current module are displayed. Using the X command by itself displays all public symbols available to CVW. Additional query words: no32bit 4.00 4.10
Keywords : kb16bitonly |
Last Reviewed: October 21, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |