Share via

/PDBSTRIPPED (Strip Private Symbols)

  • Article

 

The latest version of this topic can be found at -PDBSTRIPPED (Strip Private Symbols).

PDBSTRIPPED:pdb_file_name

  
## Remarks  
 where:  
  
 *pdb_file_name*  
 A user-specified name for the stripped program database (PDB) that the linker creates.  
  
## Remarks  
 The /PDBSTRIPPED option creates a second program database (PDB) file when you build your program image with any of the compiler or linker options that generate a PDB file ([/DEBUG](../Topic/-DEBUG%20\(Generate%20Debug%20Info\).md), [/Z7](../Topic/-Z7,%20-Zi,%20-ZI%20\(Debug%20Information%20Format\).md), /Zd, or /Zi). This second PDB file omits symbols that you would not want to ship to your customers. The second PDB file will only contain:  
  
-  Public symbols  
  
-  The list of object files and the portions of the executable to which they contribute  
  
-  Frame pointer optimization (FPO) debug records used to traverse the stack  
  
 The stripped PDB file will not contain:  
  
-  Type information  
  
-  Line number information  
  
-  Per-object file CodeView symbols such as those for functions, locals, and static data  
  
 The full PDB file will still be generated when you use /PDBSTRIPPED.  
  
 If you do not create a PDB file, /PDBSTRIPPED is ignored.  
  
### To set this linker option in the Visual Studio development environment  
  
1.  Open the project's **Property Pages** dialog box. For details, see [Setting Visual C++ Project Properties](../Topic/Working%20with%20Project%20Properties.md).  
  
2.  Click the **Linker** folder.  
  
3.  Click the **Debug** property page.  
  
4.  Modify the **Strip Private Symbols** property.  
  
### To set this linker option programmatically  
  
-  See [StripPrivateSymbols](assetId:///P:Microsoft.VisualStudio.VCProjectEngine.VCLinkerTool.StripPrivateSymbols?qualifyHint=False&autoUpgrade=True).  
  
## See Also  
 [Setting Linker Options](../Topic/Setting%20Linker%20Options.md)   
 [Linker Options](../Topic/Linker%20Options.md)