[
https://issues.apache.org/jira/browse/IMPALA-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-2619:
----------------------------------
Priority: Major (was: Critical)
> create scripts for reliable core file debugging
> -----------------------------------------------
>
> Key: IMPALA-2619
> URL: https://issues.apache.org/jira/browse/IMPALA-2619
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Affects Versions: Impala 2.3.0
> Reporter: Silvius Rus
> Assignee: Anuj Phadke
> Priority: Major
>
> These step by step instructions should be scripted.
> On the system where impalad crashed:
> {code}
> gdb -c core /path/to/impalad
> (gdb) info shared
> # Take this list of .so's and tar them up, being sure to follow symlinks:
> tar chvzf so.tar.gz <list of so files>
> # Copy the core file, impalad, impalad.debug, and so.tar.gz files in the jira
> directory on impala-desktop.
> On the system where you'll debug:
> tar xvf so.tar.gz
> gdb impalad
> # That should find and load symbols from impalad.debug automatically.
> # Tell gdb to look for the copied so's rather than the system so's
> (gdb) set sysroot /path/to/extracted/so/tar
> # Once the path is changed, then load the core file
> (gdb) core core
> # Now the core file should be debuggable on the remote system.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
