INFO:root:Processing binary file: /tmp/tmpL5sAoP/usr/lib/impala/lib/libgcc_s.so.1 INFO:root:Processing binary file: /tmp/tmpL5sAoP/usr/lib/impala/lib/libkudu_client.so.0 INFO:root:Processing binary file: /tmp/tmpL5sAoP/usr/lib/impala/lib/libstdc++.so.6 INFO:root:Processing binary file: /tmp/tmpL5sAoP/usr/lib/impala/lib/libkudu_client.so.0.1.0 INFO:root:Processing binary file: /tmp/tmpL5sAoP/usr/lib/impala/lib/libstdc++.so.6.0.20 If your system was running CentOS 6 and Cloudera's CDH5.8.0, you would need these two files: For example, for release versions of Cloudera's distribution of Impala, you can find these files here: If you obtained a minidump file from a host that had been installed using RPM packages, then you will have to retrieve matching versions of the RPM package that is installed on the host and its corresponding debuginfo package. INFO:root:Processing binary file: be/build/latest/util/libloggingsupport.so Extracting from RPMs/DEBs INFO:root:Processing binary file: be/build/latest/service/impalad INFO:root:Processing binary file: be/build/latest/service/libfesupport.so $ dump_breakpad_symbols.py -f be/build/latest/service/libfesupport.so be/build/latest/service/impalad be/build/latest/util/libloggingsupport.so -d /tmp/syms
tmp/syms is the target directory for the converted symbol files. If you compiled Impala locally and have access to the build results, you can tell the script where to search for binaries. Breakpad symbol files are identified by hashes, so you can dump symbols for multiple binaries into the same destination folder. The script will write a directory of files, which can then be used by Breakpad's minidump_stackwalk tool to resolve the symbols. The Impala repository contains a script called dump_breakpad_symbols.py, which can be used to convert debug symbols from various sources into Breakpad's own format.
in Chrome, Firefox, Android and developed as an open source project. The Breakpad library is widely used, e.g. Symbol resolution happens on the developer side, so there is no need to ship debug symbols together with Impala binaries. The resulting files are much smaller than traditional core dumps and can be collected over networks much more quickly.
) and process information (loaded modules).
They contain the crash reason, up to 8 KB of stack memory per thread, plus environment (OS, CPU. Text and Code: ABAP, ADA, ADP, AHK, AS, AS3, ASC, ASCX, ASM, ASP, AWK, BAS, BASH, BASH_LOGIN, BASH_LOGOUT, BASH_PROFILE, BASHRC, BAT, BIB, BSH, BUILD, BUILDER, C, C++, CAPFILE, CBK, CC, CFC, CFM, CFML, CL, CLJ, CMAKE, CMD, COFFEE, CPP, CPT, CPY, CS, CSHTML, CSON, CSPROJ, CSS, CTP, CXX, D, DDL, DI.Minidumps are small, concise crash dumps, written by the Google Breakpad library. Microsoft Office (Word, PowerPoint, Excel): CSV, DIC, DOC, DOCM, DOCX, DOTM, DOTX, POT, POTM, POTX, PPS, PPSM, PPSX, PPT, PPTM, PPTX, XD, XLS, XLSB, XLSX, SLTX Note: can only show thumbnails or image previews if the image size is less than 100 MB (approximately 12000 x 8000 pixels).