office-gobmx/external/breakpad
Stephan Bergmann 935f76d0ed Use proper ucontext_t in external/breakpad
SUSv4 merely claims that ucontext_t is defined as a structure type (in
<signal.h>), and at least /usr/include/sys/ucontext.h in
glibc-headers-2.26-15.fc27.x86_64 now defines it as

  typedef struct ucontext_t { ... } ucontext_t;

instead of as

  typedef struct ucontext { ... } ucontext_t;

as was done in older glibc, so referring to it as "struct ucontext" (C/C++) or
"ucontext" (C++) no longer works.

Change-Id: I3d515a4ce7e5a49d0277136cad2b982bdf799ac5
2017-11-14 18:21:22 +01:00
..
breakpad-stackwalk.patch.1
breakpad-use-correct-http-header.patch.1
breakpad-wshadow.patch.1
breakpad-wshadow2.patch.1
ExternalProject_breakpad.mk
Makefile
Module_breakpad.mk
README
StaticLibrary_breakpad.mk
ubsan.patch
ucontext.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"