The information in this article applies to:
SUMMARYThis article explains how the IMAGEHLP library analyzes symbolic information depending on the type of symbols that are generated for any executable file or dynamic link library (DLL). The symbol type may be particularly useful for an application which needs symbolic information. MORE INFORMATIONFollowing are two important components involved in using IMAGEHLP.
If you are using the Microsoft Visual C++ development environment, select the following linker settings in the Link tab under Project Settings:
If the debug information is embedded inside an executable file, a DLL, or is stripped and placed in a .dbg file, the Imagehlp.dll is sufficient for using all symbol handler functions. The symbol type information can be obtained by using the SymGetModuleInfo() IMAGEHLP function where SymType is the corresponding member in the IMAGEHLP_MODULE structure. If SymType is set to SymPdb, IMAGEHLP will dynamically load one of the available Mspdbxx.dlls or Msdbi.dll that can analyze the debug format. The symbol type is SymPdb if the CodeView symbols are placed in a .pdb file. If the CodeView symbols are embedded inside an executable file, a DLL, or stripped and placed in a .dbg file, the symbol type will be SymCv. If the symbol type is SymCv, SymCoff, SymSym, or anything other than SymPdb, then Imagehlp.dll uses all symbol handler functions. REFERENCESQ121366: INFO: PDB and DBG Files - What They Are and How They WorkFor more information on IMAGEHLP_MODULE structure, please refer to the SDK documentation. Additional query words:
Keywords : kbAPI kbDebug kbImgHlp kbKernBase kbNTOS400 kbWinOS2000 kbWinOS95 kbWinOS98 kbDSupport kbGrpKernBase |
Last Reviewed: January 11, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |