You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2024/02/08 21:19:00 UTC
[jira] [Created] (IMPALA-12799) Update "Debugging Impala Minidumps" Wiki page
Joe McDonnell created IMPALA-12799:
--------------------------------------
Summary: Update "Debugging Impala Minidumps" Wiki page
Key: IMPALA-12799
URL: https://issues.apache.org/jira/browse/IMPALA-12799
Project: IMPALA
Issue Type: Improvement
Components: Docs
Affects Versions: Impala 4.3.0
Reporter: Joe McDonnell
The Wiki page "Debugging Impala Minidumps" is a bit stale and could use some modifications. Specifically:
# In IMPALA-12125, we added the ability to dump symbols for OS packages that don't have a separate symbols package. Some commercial distributions of Impala such as Cloudera's CDP produce this type of packaging.
# The documentation for dumping symbols from OS packages references packages from Cloudera's CDH 5.8. This is an old version, and it would be useful for the example to be on a more up-to-date version.
# The section "Extracting from Jenkins build artifacts" does not seem to be useful anymore.
# minidump-2-core is definitely a useful workflow and filling in information about it would be useful. In particular, a valuable technique is to use minidump-2-core, then run gdb with the unstripped binary. Examining the stack can yield the query / thread that crashed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)