Platform SDK: Debugging and Error Handling

SplitSymbols

The SplitSymbols function strips symbols from the specified image.

BOOL SplitSymbols(
  PSTR ImageName,    
  PSTR SymbolsPath,  
  PSTR SymbolFilePath,  
  DWORD Flags         
);

Parameters

ImageName
[in] Pointer to a null-terminated string that specifies the name of the image from which to split symbols.
SymbolsPath
[in] Pointer to a null-terminated string that specifies a subdirectory for storing symbols. This parameter is optional.
SymbolFilePath
[in] Pointer to a null-terminated string that specifies the name of the generated symbol file. This file typically has a .dbg extension.
Flags
[in] Specifies the information to be split from the image. This parameter can be zero or a combination of the following values.
Value Meaning
SPLITSYM_EXTRACT_ALL Usually, an image with the symbols split off will still contain a MISC debug directory with the name of the symbol file. Therefore, the debugger can still find the symbols. Using this flag removes this link. The end result is similar to using the -debug:none switch on the Microsoft linker.
SPLITSYM_REMOVE_PRIVATE This strips off the private CodeView symbolic information when generating the symbol file.
SPLITSYM_SYMBOLPATH_IS_SRC The symbol file path contains an alternate path to locate the .pdb file.

Return Values

If the function succeeds, the return value is TRUE.

If the function fails, the return value is FALSE. To retrieve extended error information, call GetLastError.

Remarks

The SplitSymbols function should be used when stripping symbols from an image. It will create a symbol file that all Win32-compatible debuggers understand. The format is defined in WINNT.H and consists of an image header, followed by the array of section headers, the exception information (on RISC only) or FPO information (on X86 only), and all debugging symbolic information from the image.

If the SymbolsPath parameter is NULL, the symbol file is stored in the directory where the image exists. Otherwise, it is stored in the subdirectory below SymbolsPath that matches the extension of the image. Using this method reduces the chances of symbol file collision. For example, the symbols for myapp.exe will be in the SymbolsPath\exe directory and the symbols for myapp.dll will be in the SymbolsPath\dll directory.

Requirements

  Windows NT/2000: Requires Windows NT 4.0 or later.
  Windows 95/98: Requires Windows 95 or later. Available as a redistributable for Windows 95.
  Header: Declared in Imagehlp.h.
  Library: Use Imagehlp.lib.

See Also

Image Help Library Overview, ImageHlp Functions