office-gobmx/external/breakpad
..
0001-Handle-race-between-ExceptionHandler-SignalHandler-a.patch.1
breakpad-dump_syms.patch.1
breakpad-no-env.patch.1
breakpad-stackwalk.patch.1
breakpad-use-correct-http-header.patch.1
breakpad-wshadow.patch.1
c++20-allocator.patch
dump_syms.sln
dump_syms.vcxproj
ExternalProject_breakpad.mk
include.patch
Makefile
Module_breakpad.mk
README
sanitizer.patch
SIGSTKSZ.patch
StaticLibrary_breakpad.mk
ubsan.patch
UnpackedTarball_breakpad.mk

Google breakpad crash-reporting library

https://chromium.googlesource.com/breakpad/breakpad

When this is enabled and soffice.bin crashes, a "mini-dump" file is written
as "instdir/crash/*.dmp".

There is an UI to upload the mini-dump to a TDF server but of course
that only makes sense if the server has symbols available that match
the build, which is not the case if you have built LO yourself.

If you want to get the backtrace from local mini-dump files:

* with Visual Studio:
  1. open the *.dmp file from the Visual Studio IDE File->Open->File
  2. then click "Debug Native Only"

* otherwise:
  1. run "make symbols" to extract the debuginfo from the binaries
  2. run "workdir/UnpackedTarball/breakpad/src/processor/minidump_stackwalk foo.dmp workdir/symbols"