Using SendPdbs to Automatically Upload Symbol Files

Many customers automate the upload of Windows symbols and executables using the BugSplat utility SendPdbs.exe.
Each build of your product that is used to send crash reports must have an exact set of matching exe/symbol files uploaded to BugSplat. Typically you will provide a unique BugSplat application name/version for each build.
Feel free to send symbols to BugSplat for every build on your build/integration server. There is no limit on the total amount of symbols you can post to BugSplat. But by default, any single symbol file must be smaller than 2gb and any single symbol store (identified by an application name and version) must be less than 4gb. Enterprise customers can increase these limits.
Credentials can be provided to SendPdbs via the /u and /p command line arguments. Alternatively you can save these credentials in the Windows Credentials Manager. To use values from Windows Credential Manager, create a new Generic Credentials entry and provide the entry name as the value for the /credentials argument.
Note that BugSplat will automatically remove unreferenced symbols in large symbol sets. If your database contains more than 5 gigabytes of symbol data, our cleanup algorithm will automatically remove symbols that haven't been referenced by a crash report in more than 90 days. Additionally, newly posted symbols not referenced by a crash report within 15 days will be removed.
You can download the BugSplatSendPdbs file by clicking here.
Running SendPdbs.exe in a command window without any arguments show the following usage information: 
1
 USAGE: This utility searches your build tree for Windows symbol/executable
2
  files and uploads them to the BugSplat server.
3
​
4
    Specify BugSplat credentials using either:
5
    /u USER
6
    /p PASSWORD
7
    -or-
8
    /credentials WINDOWS-CREDENTIAL-MANAGER-GENERIC-CREDENTIALS
9
​
10
  Other required parameters:
11
    /b DATABASE  BugSplat database
12
    /a APPNAME   AppName for the symbol files (e.g. /a MyApp)
13
    /v VERSION   Version number of AppName (e.g. /v 1.0), required if /l not set
14
    /l LIBRARY   Library from which to extract file version info (e.g. /l MyApp.exe), required if /v not set
15
​
16
  Upload is the default action, modify using the following parameters:
17
    /s           Search subdirectories, default off
18
    /d PATH      Folder to search, defaults to current folder
19
    /f FILESPEC  Files to search, defaults to "*.pdb;*.dll;*.exe"
20
    /compression LEVEL  Optimal, fastest, or nocompression, defaults to Optimal
21
    /threads NUM Threads used during upload, defaults to 20
22
    /c RETRIES   Maximum retries to attempt for each file upload, defaults to 3.
23
​
24
  To remove symbols from BugSplat use the following single parameter:
25
    /r           Removes all symbols for specified AppName, AppVersion, Database
26
​
27
  The log level can be modified with:
28
    /verbose     Use for additional diagnostics
Copied!

Using BugSplat's public database

How and why to Group Crashes

Last modified 4mo ago

Copy link