forked from amazingfate/loongoffice
1e51a325a8
...which is a problem presumably since GCC 13 trunk <https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=6f038efd93593da6e661b829d1bd3877e75550f1> "libstdc++: Avoid including <cstdint> for std::char_traits". (All the broken C++ code used unqualified uintptr_t etc. rather than std::uintptr_t etc., so I deemed it more appropriate to include <stdint.h> rather than <cstdint>.) Change-Id: Id9dfc383c5986126a425971c4557b90ac45ac963 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134760 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
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"