Support in minidump_stackwalk for fetching debug symbols from arbitrary sources
by invoking a user-provided command instead of looking in a specific local filesystem
directory. We use this to fetch debug symbols on-demand from an archive hosted in S3.

A python script which fetches debug symbols from a symbol server with a given HTTP URL

Usage

Early in your app's startup code, create an instance of google_breakpad::ExceptionHandler. This
is defined separately for each platform in client/<platform>/handler/exception_handler.h

When the app crashes, it will write a .dmp file to the directory specified when the ExceptionHandler
object was created.

When building a release build of your app, run the dump_syms tool on the generated DLLs and binaries
to produce .sym files which contain mappings from program locations to source locations.

Upload the .sym files to a location which is accessible via a HTTP URL. See this StackOverflow comment for details of the expected structure of the symbol server

When your app crashes on a user's system, get the .dmp file and use minidump_stackwalk to produce a stacktrace
from the .dmp file.

You can also debug the .dmp files in Visual Studio on Windows.

Getting a stacktrace from a minidump

When you have a .dmp file captured by the breakpad library after an application crashes and have
uploaded it to a location accessible via a HTTP URL, you can use the minidump_stackwalk tool to extract
a stack trace from the minidump.