Files
loongoffice/external/breakpad
Jan-Marek Glogowski 8a4173987e WASM: add initial support for Emscripten cross build
- configure with:
- --host=wasm64-local-emscripten
- had to make a few externals optional, so adding:
  - --disable-nss
  - --disable-cmis
  - --disable-curl

Change-Id: I48d1c73d2675ad2e2beaf2c341578199efbd24ee
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111130
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens <thorsten.behrens@allotropia.de>
2021-05-05 21:14:54 +02:00
..

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"