Mailing-List: contact dev-help@impala.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@impala.apache.org
MIME-Version: 1.0
Message-ID: <pony-09eec4a8e1a345c04e7c13b8a3ebc4ed277c1b23-c3dc7daee83d786b4d92b1f3f3ffdcde5160ec19@dev.impala.apache.org>
Subject: Re: Impala minidump dump_breakpad_symbols
References: <CAM_aD9dBMa6d9-O8M5umvj+G-=DJz_g21Wr01R4friTvP=g-bQ@mail.gmail.com> <pony-09eec4a8e1a345c04e7c13b8a3ebc4ed277c1b23-04c0d46c0b885c72f4356b25bcd36a3e77852858@dev.impala.apache.org>
 <pony-09eec4a8e1a345c04e7c13b8a3ebc4ed277c1b23-f32e5cd9eb560bf21a8bbfaa282e50a30825728f@dev.impala.apache.org>
 <CAM_aD9cTPtpBhidxrzoV3qBHvBq+uea2jmu_hWzooUFCoZ861Q@mail.gmail.com>
From: "sanysandish@gmail.com"<sanysandish@gmail.com>
In-Reply-To: <CAM_aD9dBMa6d9-O8M5umvj+G-=DJz_g21Wr01R4friTvP=g-bQ@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Date: Wed, 29 Nov 2017 04:36:27 -0000
To: <dev@impala.apache.org>
archived-at: Wed, 29 Nov 2017 04:36:34 -0000


On 2017-11-28 21:01, Lars Volker <lv@cloudera.com> wrote: 
> The resolved minidump looks truncated, as does the output of minidump
> stackwalk. This could indicate that the minidump got corrupted. How did you
> generate the minidump?
> 
> On Nov 28, 2017 02:20, "sanysandish@gmail.com" <sanysandish@gmail.com>
> wrote:
> 
> >
> > Thank you, Lars Volker, for quick response's
> >
> > The end content of /tmp/resolved.txt  file:
> >
> > [ec2-user@jenkins tmp]$ tail -20f /tmp/resolved.txt
> >     rbp = 0x00007fd7d4fdf220   rsp = 0x00007fc10d6ad270
> >      r8 = 0x00007fd7d4fdf220    r9 = 0x00000000ffffffff
> >     r10 = 0x00007fc10d6ad3d0   r11 = 0x0000000000000202
> >     r12 = 0x0000000000000006   r13 = 0x00007fc10d6ad3d0
> >     r14 = 0xffffffffffffff92   r15 = 0x00007fc10d6ad400
> >     rip = 0x00007fdb5e2ffa82
> >     Found by: given as instruction pointer in context
> >
> > Thread 960
> >  0  0x7fdb5e2ffa82
> >     rax = 0xfffffffffffffdfc   rdx = 0x0000000000000001
> >     rcx = 0xffffffffffffffff   rbx = 0x0000000010d33e20
> >     rsi = 0x0000000000000189   rdi = 0x0000000010d33e4c
> >     rbp = 0x00007fc0f3e7a740   rsp = 0x00007fc0f3e7a6b0
> >      r8 = 0x0000000010d33e20    r9 = 0x00000000ffffffff
> >     r10 = 0x00007fc0f3e7a740   r11 = 0x0000000000000202
> >     r12 = 0x0000000000000001   r13 = 0x00007fc0f3e7a740
> >     r14 = 0xffffffffffffff92   r15 = 0x0000000022217000
> >     rip = 0x00007fdb5e2ffa82
> >     Found by: given as instruction pointer in context
> >
> > Output of find syms/impalad:
> > [ec2-user@jenkins tmp]$ find syms/impalad
> > syms/impalad
> > syms/impalad/73318DB4729C07530B7338E67EA255AB0
> > syms/impalad/73318DB4729C07530B7338E67EA255AB0/impalad.sym
> >
> > These are the steps I had followed:
> > Step-1:
> > I followed exact steps from this https://cwiki.apache.org/confl
> > uence/display/IMPALA/Building+Impala and also followed "build
> > native-toolchain from scratch" https://cwiki.apache.org/confl
> > uence/display/IMPALA/Building+native-toolchain+from+scratch+
> > and+using+with+Impala
> >
> > Step-2:
> > Env:
> > export IMPALA_HOME=/home/ec2-user/impala-setup/Impala
> > export PATH=$PATH:$IMPALA_HOME/bin
> > export KUDU_IS_SUPPORTED=false
> > export KUDU_CLIENT_DIR=/opt/kudu/
> >
> > Get breakpad symbols:
> > dump_breakpad_symbols.py -b be/build/ --dump_syms
> > $IMPALA_HOME/toolchain/breakpad-1b704857f1e78a864e6942e613457e55f1aecb60-p3/bin/dump_syms
> > -d /tmp/syms
> >
> > rm /tmp/resolved.txt
> >
> > Run minidump_stackwalk:
> > $IMPALA_HOME/toolchain/breakpad-1b704857f1e78a864e6942e61345
> > 7e55f1aecb60-p3/bin/minidump_stackwalk /home/ec2-user/64811560-8bae-a67f-22f961c1-45bf52a3.dmp
> > /tmp/syms > /tmp/resolved.txt
> >
> >
> > Please let me know If I have missed any steps??
> >
> >
> >
> Thanks you Lars Volker,
I took few new .dmp files and ran through stackwalk.
here is last few lines from the resolver:

Loaded modules:
0x00400000 - 0x0283efff  impalad  ???  (main)  (WARNING: No symbols, impalad, 21AA452CEF0F8C034C7E78A639190ED40)
0x7fce0a33b000 - 0x7fce0a543fff  libgssapiv2.so.3.0.0  ???
0x7fce0a544000 - 0x7fce0a748fff  libplain.so.3.0.0  ???
0x7fce0a749000 - 0x7fce0a94dfff  liblogin.so.3.0.0  ???
0x7fce0a94e000 - 0x7fce0ad0bfff  libdb-5.3.so  ???
0x7fce0ad0c000 - 0x7fce0af12fff  libsasldb.so.3.0.0  ???
0x7fce0af13000 - 0x7fce0b118fff  libanonymous.so.3.0.0  ???
0x7fce0b919000 - 0x7fce0bb79fff  libpcre.so.1.2.0  ???
0x7fce0bb7a000 - 0x7fce0bd9efff  libselinux.so.1  ???
0x7fce0bda1000 - 0x7fce0bfa4fff  libkeyutils.so.1.5  ???
0x7fce0bfa5000 - 0x7fce0c1b2fff  libkrb5support.so.0.1  ???
0x7fce0c1b3000 - 0x7fce0c3b5fff  libfreebl3.so  ???
0x7fce0c3b6000 - 0x7fce0c5cbfff  libz.so.1.2.7  ???
0x7fce0c5cc000 - 0x7fce0c7fefff  libk5crypto.so.3.1  ???
0x7fce0c7ff000 - 0x7fce0ca02fff  libcom_err.so.2.1  ???
0x7fce0ca03000 - 0x7fce0cceafff  libkrb5.so.3.3  ???
0x7fce0cceb000 - 0x7fce0cf37fff  libgssapi_krb5.so.2.2  ???
0x7fce0cf38000 - 0x7fce0d140fff  libcrypt-2.17.so  ???
0x7fce0d16f000 - 0x7fce0d386fff  libresolv-2.17.so  ???
0x7fce0d389000 - 0x7fce0d746fff  libc-2.17.so  ???  (WARNING: No symbols, libc-2.17.so, E42D1DFF35CF1831960C5EA195CEB1360)
0x7fce0d74c000 - 0x7fce0d963fff  libpthread-2.17.so  ???  (WARNING: No symbols, libpthread-2.17.so, 9B139160D961AA018425DBC16B7F51D40)

I think I'm still not getting symbols for impala??