date:20171128

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread sanysand...@gmail.com



On 2017-11-29 11:03, Vincent Tran  wrote: 
> You are going to have to dump the symbols using the RPMs that match this
> version here:
> /opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.34/lib/impala/
> sbin-retail/impalad
> 
> 
> Follow "Extracting from RPMs" section of this guide:
> 
> https://cwiki.apache.org/confluence/display/IMPALA/Debugging+Impala+Minidumps
> 
> On Wed, Nov 29, 2017 at 12:28 AM, sanysand...@gmail.com <
> sanysand...@gmail.com> wrote:
> 
> >
> >
> > On 2017-11-29 10:31, Vincent Tran  wrote:
> > > Hi Sandish,
> > >
> > > Did you get the minidump from the minicluster of this private build? It
> > > looks like the hash of your private build symbols and the one from the md
> > > do not match.
> > >
> > > You can turn the md into a core to see the original binary version that
> > > generated it:
> > >
> > > /bin/minidump-2-core
> > > 11850fc8-c7ec-dd15-15ba7314-1926301a.dmp >
> > > 11850fc8-c7ec-dd15-15ba7314-1926301a.core
> > > If you open the resulting core file in gdb, what does the last line say?
> > >
> > >
> > >
> > >
> > >
> > > On Nov 28, 2017 11:36 PM, "sanysand...@gmail.com"  > >
> > > wrote:
> > >
> > > >
> > > >
> > > > On 2017-11-28 21:01, Lars Volker  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, "sanysand...@gmail.com" <
> > sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
> > > > > >  r8 = 0x7fd7d4fdf220r9 = 0x
> > > > > > r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> > > > > > r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> > > > > > r14 = 0xff92   r15 = 0x7fc10d6ad400
> > > > > > rip = 0x7fdb5e2ffa82
> > > > > > Found by: given as instruction pointer in context
> > > > > >
> > > > > > Thread 960
> > > > > >  0  0x7fdb5e2ffa82
> > > > > > rax = 0xfdfc   rdx = 0x0001
> > > > > > rcx = 0x   rbx = 0x10d33e20
> > > > > > rsi = 0x0189   rdi = 0x10d33e4c
> > > > > > rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
> > > > > >  r8 = 0x10d33e20r9 = 0x
> > > > > > r10 = 0x7fc0f3e7a740   r11 = 0x0202
> > > > > > r12 = 0x0001   r13 = 0x7fc0f3e7a740
> > > > > > r14 = 0xff92   r15 = 0x22217000
> > > > > > rip = 0x7fdb5e2ffa82
> > > > > > 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-1b704857f1e78a864e6942e61345
> > > > 7e55f1aecb60-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-a
> > > > 67f-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:
> > > > 0x0040 - 0x0283efff  impalad  ???  (main)  (WARNING: No symbols,
> > > > impalad, 21AA452CEF0F8C034C7E78A639190ED40)
> > > > 0x7fce0a33b000 - 0x7fce0a543fff  libgssapiv2.so.3.0.0  ???
> > > > 0x7fce0a544000 - 0x7fce0a748fff  libplain.so.3.0.0  ???
> > > > 0x7fce0a749000 - 0

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread Vincent Tran

You are going to have to dump the symbols using the RPMs that match this
version here:
/opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.34/lib/impala/
sbin-retail/impalad


Follow "Extracting from RPMs" section of this guide:

https://cwiki.apache.org/confluence/display/IMPALA/Debugging+Impala+Minidumps

On Wed, Nov 29, 2017 at 12:28 AM, sanysand...@gmail.com <
sanysand...@gmail.com> wrote:

>
>
> On 2017-11-29 10:31, Vincent Tran  wrote:
> > Hi Sandish,
> >
> > Did you get the minidump from the minicluster of this private build? It
> > looks like the hash of your private build symbols and the one from the md
> > do not match.
> >
> > You can turn the md into a core to see the original binary version that
> > generated it:
> >
> > /bin/minidump-2-core
> > 11850fc8-c7ec-dd15-15ba7314-1926301a.dmp >
> > 11850fc8-c7ec-dd15-15ba7314-1926301a.core
> > If you open the resulting core file in gdb, what does the last line say?
> >
> >
> >
> >
> >
> > On Nov 28, 2017 11:36 PM, "sanysand...@gmail.com"  >
> > wrote:
> >
> > >
> > >
> > > On 2017-11-28 21:01, Lars Volker  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, "sanysand...@gmail.com" <
> sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
> > > > >  r8 = 0x7fd7d4fdf220r9 = 0x
> > > > > r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> > > > > r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> > > > > r14 = 0xff92   r15 = 0x7fc10d6ad400
> > > > > rip = 0x7fdb5e2ffa82
> > > > > Found by: given as instruction pointer in context
> > > > >
> > > > > Thread 960
> > > > >  0  0x7fdb5e2ffa82
> > > > > rax = 0xfdfc   rdx = 0x0001
> > > > > rcx = 0x   rbx = 0x10d33e20
> > > > > rsi = 0x0189   rdi = 0x10d33e4c
> > > > > rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
> > > > >  r8 = 0x10d33e20r9 = 0x
> > > > > r10 = 0x7fc0f3e7a740   r11 = 0x0202
> > > > > r12 = 0x0001   r13 = 0x7fc0f3e7a740
> > > > > r14 = 0xff92   r15 = 0x22217000
> > > > > rip = 0x7fdb5e2ffa82
> > > > > 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-1b704857f1e78a864e6942e61345
> > > 7e55f1aecb60-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-a
> > > 67f-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:
> > > 0x0040 - 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  ???
> > > 0x7fce0bb7a0

[IMPALA-3060] Supports IS [NOT] NULL feature for complex types(e.g. STRUCT)

2017-11-28 Thread Jin Chul Kim

Hi,

I would like to get your advice before taking over the ticket.
https://issues.apache.org/jira/browse/IMPALA-3060

I already know how works IS [NOT] NULL for primitive type, but I don't know
null status for complex types. As far as I know, it is impossible to assign
null to struct column directly(I mean logically). When do we define a
struct column is null? Please see the example below.

I asked the following questions to Hive user mailing list. I haven't got
any response yet, but I would like to hear your opinion also. Thanks.

Best regards,
Jinchul

--
- The following example is only available on Hive.

May I know the meaning of IS [NOT] NULL for a complex type such as STRUCT?
As far as I know, we cannot assign NULL to struct directly.
So, I expected them:
1) NULL returns if any of the elements in struct has NULL
2) NULL returns if all of the elements in struct have NULL

By the way, my assumption was wrong in my example below. Could you let me
know when struct is null?

For example,
create table t1(a struct);
insert into t1 select named_struct('c1', 100, 'c2', 'test', 'c3', 1.234);
insert into t1 select named_struct('c1', cast(null as int), 'c2', 'test',
'c3', 1.234);
insert into t1 select named_struct('c1', 100, 'c2', cast(null as string),
'c3', 1.234);
insert into t1 select named_struct('c1', 100, 'c2', 'test', 'c3', cast(null
as double));
insert into t1 select named_struct('c1', cast(null as int), 'c2', cast(null
as string), 'c3', cast(null as double));
select a is null, * from t1;
false   {"c1":100,"c2":"test","c3":1.234}
false   {"c1":null,"c2":"test","c3":1.234}
false   {"c1":100,"c2":null,"c3":1.234}
false   {"c1":100,"c2":"test","c3":null}
false   {"c1":null,"c2":null,"c3":null}

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread sanysand...@gmail.com



On 2017-11-29 10:33, Lars Volker  wrote: 
> Yeah, this line indicates that you didn't have the right symbols in your
> syms folder:
> 
> 0x0040 - 0x0283efff  impalad  ???  (main)  (WARNING: No symbols,
> impalad, 21AA452CEF0F8C034C7E78A639190ED40)
> 
> You may want to try running dump_breakpad_symbols.py again to get the
> correct symbols.
> 
> On Tue, Nov 28, 2017 at 9:01 PM, Vincent Tran  wrote:
> 
> > Hi Sandish,
> >
> > Did you get the minidump from the minicluster of this private build? It
> > looks like the hash of your private build symbols and the one from the md
> > do not match.
> >
> > You can turn the md into a core to see the original binary version that
> > generated it:
> >
> > /bin/minidump-2-core
> > 11850fc8-c7ec-dd15-15ba7314-1926301a.dmp >
> > 11850fc8-c7ec-dd15-15ba7314-1926301a.core
> > If you open the resulting core file in gdb, what does the last line say?
> >
> >
> >
> >
> >
> > On Nov 28, 2017 11:36 PM, "sanysand...@gmail.com" 
> > wrote:
> >
> > >
> > >
> > > On 2017-11-28 21:01, Lars Volker  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, "sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
> > > > >  r8 = 0x7fd7d4fdf220r9 = 0x
> > > > > r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> > > > > r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> > > > > r14 = 0xff92   r15 = 0x7fc10d6ad400
> > > > > rip = 0x7fdb5e2ffa82
> > > > > Found by: given as instruction pointer in context
> > > > >
> > > > > Thread 960
> > > > >  0  0x7fdb5e2ffa82
> > > > > rax = 0xfdfc   rdx = 0x0001
> > > > > rcx = 0x   rbx = 0x10d33e20
> > > > > rsi = 0x0189   rdi = 0x10d33e4c
> > > > > rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
> > > > >  r8 = 0x10d33e20r9 = 0x
> > > > > r10 = 0x7fc0f3e7a740   r11 = 0x0202
> > > > > r12 = 0x0001   r13 = 0x7fc0f3e7a740
> > > > > r14 = 0xff92   r15 = 0x22217000
> > > > > rip = 0x7fdb5e2ffa82
> > > > > 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-1b704857f1e78a864e6942e61345
> > > 7e55f1aecb60-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-a
> > > 67f-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:
> > > 0x0040 - 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  ???
> > > 0x7fce0bda10

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread sanysand...@gmail.com



On 2017-11-29 10:31, Vincent Tran  wrote: 
> Hi Sandish,
> 
> Did you get the minidump from the minicluster of this private build? It
> looks like the hash of your private build symbols and the one from the md
> do not match.
> 
> You can turn the md into a core to see the original binary version that
> generated it:
> 
> /bin/minidump-2-core
> 11850fc8-c7ec-dd15-15ba7314-1926301a.dmp >
> 11850fc8-c7ec-dd15-15ba7314-1926301a.core
> If you open the resulting core file in gdb, what does the last line say?
> 
> 
> 
> 
> 
> On Nov 28, 2017 11:36 PM, "sanysand...@gmail.com" 
> wrote:
> 
> >
> >
> > On 2017-11-28 21:01, Lars Volker  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, "sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
> > > >  r8 = 0x7fd7d4fdf220r9 = 0x
> > > > r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> > > > r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> > > > r14 = 0xff92   r15 = 0x7fc10d6ad400
> > > > rip = 0x7fdb5e2ffa82
> > > > Found by: given as instruction pointer in context
> > > >
> > > > Thread 960
> > > >  0  0x7fdb5e2ffa82
> > > > rax = 0xfdfc   rdx = 0x0001
> > > > rcx = 0x   rbx = 0x10d33e20
> > > > rsi = 0x0189   rdi = 0x10d33e4c
> > > > rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
> > > >  r8 = 0x10d33e20r9 = 0x
> > > > r10 = 0x7fc0f3e7a740   r11 = 0x0202
> > > > r12 = 0x0001   r13 = 0x7fc0f3e7a740
> > > > r14 = 0xff92   r15 = 0x22217000
> > > > rip = 0x7fdb5e2ffa82
> > > > 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-1b704857f1e78a864e6942e61345
> > 7e55f1aecb60-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-a
> > 67f-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:
> > 0x0040 - 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  ???
> > 0x7f

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread Lars Volker

Yeah, this line indicates that you didn't have the right symbols in your
syms folder:

0x0040 - 0x0283efff  impalad  ???  (main)  (WARNING: No symbols,
impalad, 21AA452CEF0F8C034C7E78A639190ED40)

You may want to try running dump_breakpad_symbols.py again to get the
correct symbols.

On Tue, Nov 28, 2017 at 9:01 PM, Vincent Tran  wrote:

> Hi Sandish,
>
> Did you get the minidump from the minicluster of this private build? It
> looks like the hash of your private build symbols and the one from the md
> do not match.
>
> You can turn the md into a core to see the original binary version that
> generated it:
>
> /bin/minidump-2-core
> 11850fc8-c7ec-dd15-15ba7314-1926301a.dmp >
> 11850fc8-c7ec-dd15-15ba7314-1926301a.core
> If you open the resulting core file in gdb, what does the last line say?
>
>
>
>
>
> On Nov 28, 2017 11:36 PM, "sanysand...@gmail.com" 
> wrote:
>
> >
> >
> > On 2017-11-28 21:01, Lars Volker  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, "sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
> > > >  r8 = 0x7fd7d4fdf220r9 = 0x
> > > > r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> > > > r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> > > > r14 = 0xff92   r15 = 0x7fc10d6ad400
> > > > rip = 0x7fdb5e2ffa82
> > > > Found by: given as instruction pointer in context
> > > >
> > > > Thread 960
> > > >  0  0x7fdb5e2ffa82
> > > > rax = 0xfdfc   rdx = 0x0001
> > > > rcx = 0x   rbx = 0x10d33e20
> > > > rsi = 0x0189   rdi = 0x10d33e4c
> > > > rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
> > > >  r8 = 0x10d33e20r9 = 0x
> > > > r10 = 0x7fc0f3e7a740   r11 = 0x0202
> > > > r12 = 0x0001   r13 = 0x7fc0f3e7a740
> > > > r14 = 0xff92   r15 = 0x22217000
> > > > rip = 0x7fdb5e2ffa82
> > > > 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-1b704857f1e78a864e6942e61345
> > 7e55f1aecb60-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-a
> > 67f-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:
> > 0x0040 - 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  ???
> > 0x7fce0c7ff0

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread Vincent Tran

Hi Sandish,

Did you get the minidump from the minicluster of this private build? It
looks like the hash of your private build symbols and the one from the md
do not match.

You can turn the md into a core to see the original binary version that
generated it:

/bin/minidump-2-core
11850fc8-c7ec-dd15-15ba7314-1926301a.dmp >
11850fc8-c7ec-dd15-15ba7314-1926301a.core
If you open the resulting core file in gdb, what does the last line say?





On Nov 28, 2017 11:36 PM, "sanysand...@gmail.com" 
wrote:

>
>
> On 2017-11-28 21:01, Lars Volker  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, "sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
> > >  r8 = 0x7fd7d4fdf220r9 = 0x
> > > r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> > > r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> > > r14 = 0xff92   r15 = 0x7fc10d6ad400
> > > rip = 0x7fdb5e2ffa82
> > > Found by: given as instruction pointer in context
> > >
> > > Thread 960
> > >  0  0x7fdb5e2ffa82
> > > rax = 0xfdfc   rdx = 0x0001
> > > rcx = 0x   rbx = 0x10d33e20
> > > rsi = 0x0189   rdi = 0x10d33e4c
> > > rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
> > >  r8 = 0x10d33e20r9 = 0x
> > > r10 = 0x7fc0f3e7a740   r11 = 0x0202
> > > r12 = 0x0001   r13 = 0x7fc0f3e7a740
> > > r14 = 0xff92   r15 = 0x22217000
> > > rip = 0x7fdb5e2ffa82
> > > 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-1b704857f1e78a864e6942e61345
> 7e55f1aecb60-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-a
> 67f-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:
> 0x0040 - 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 s

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread sanysand...@gmail.com



On 2017-11-28 21:01, Lars Volker  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, "sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
> >  r8 = 0x7fd7d4fdf220r9 = 0x
> > r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> > r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> > r14 = 0xff92   r15 = 0x7fc10d6ad400
> > rip = 0x7fdb5e2ffa82
> > Found by: given as instruction pointer in context
> >
> > Thread 960
> >  0  0x7fdb5e2ffa82
> > rax = 0xfdfc   rdx = 0x0001
> > rcx = 0x   rbx = 0x10d33e20
> > rsi = 0x0189   rdi = 0x10d33e4c
> > rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
> >  r8 = 0x10d33e20r9 = 0x
> > r10 = 0x7fc0f3e7a740   r11 = 0x0202
> > r12 = 0x0001   r13 = 0x7fc0f3e7a740
> > r14 = 0xff92   r15 = 0x22217000
> > rip = 0x7fdb5e2ffa82
> > 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:
0x0040 - 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??

Re: Protocol with re: to reverting previous patches

2017-11-28 Thread David Knupp


Thanks Sailesh!


Sailesh Mukil 
November 28, 2017 at 2:20 PM
Yes, that's how I've usually done it.


David Knupp 
November 28, 2017 at 2:16 PM
Seems like a silly question, but I just want to make sure I do this right.

IMPALA-6239 was filed because the patch for IMPALA-6068 introduced a 
regression. As a result, the patch was reverted: 
https://github.com/apache/incubator-impala/commit/d1c9510


Presumably, I should now just resolve IMPALA-6239 and reopen 
IMPALA-6068with a pointer to the reverted commit?

Re: Protocol with re: to reverting previous patches

2017-11-28 Thread Sailesh Mukil

Yes, that's how I've usually done it.

On Tue, Nov 28, 2017 at 2:16 PM, David Knupp  wrote:

> Seems like a silly question, but I just want to make sure I do this right.
>
> IMPALA-6239 was filed because the patch for IMPALA-6068 introduced a
> regression. As a result, the patch was reverted:
> https://github.com/apache/incubator-impala/commit/d1c9510
>
> Presumably, I should now just resolve IMPALA-6239 and reopen
> IMPALA-6068with a pointer to the reverted commit?
>
> --
> David Knupp | Software Engineer
> Cloudera Inc., 433 California Street #1100. San Francisco, CA 94104
> 
>
>  glink&utm_campaign=reach>
>

Protocol with re: to reverting previous patches

2017-11-28 Thread David Knupp


Seems like a silly question, but I just want to make sure I do this right.

IMPALA-6239 was filed because the patch for IMPALA-6068 introduced a 
regression. As a result, the patch was reverted: 
https://github.com/apache/incubator-impala/commit/d1c9510


Presumably, I should now just resolve IMPALA-6239 and reopen 
IMPALA-6068with a pointer to the reverted commit?


--
David Knupp | Software Engineer
Cloudera Inc., 433 California Street #1100. San Francisco, CA 94104

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread Jim Apple

This conversation is happening on user@

On Mon, Nov 27, 2017 at 7:14 PM, Sandish Kumar  wrote:
> Hi Team,
>
> I'm trying to get minidump_stackwalk results with dump breakpad symbols,
> but symbols are not showing in results file, below are the steps which I
> followed. Can someone verify or give me steps to get symbols in minidump_
> stackwalk results ??
>
>
> Steps:
> dump_breakpad_symbols.py -b be/build/ --dump_syms
> $IMPALA_HOME/toolchain/breakpad-1b704857f1e78a864e6942e613457e55f1aecb60-p3/bin/dump_syms
> -d /tmp/syms
>
> $IMPALA_HOME/toolchain/breakpad-1b704857f1e78a864e6942e613457e55f1aecb60-p3/bin/minidump_stackwalk
> .dmp /tmp/syms > /tmp/resolved.txt
>
> --
> Thanks,
> Sandish Kumar
> phData Inc

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread Lars Volker

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, "sanysand...@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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
>  r8 = 0x7fd7d4fdf220r9 = 0x
> r10 = 0x7fc10d6ad3d0   r11 = 0x0202
> r12 = 0x0006   r13 = 0x7fc10d6ad3d0
> r14 = 0xff92   r15 = 0x7fc10d6ad400
> rip = 0x7fdb5e2ffa82
> Found by: given as instruction pointer in context
>
> Thread 960
>  0  0x7fdb5e2ffa82
> rax = 0xfdfc   rdx = 0x0001
> rcx = 0x   rbx = 0x10d33e20
> rsi = 0x0189   rdi = 0x10d33e4c
> rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
>  r8 = 0x10d33e20r9 = 0x
> r10 = 0x7fc0f3e7a740   r11 = 0x0202
> r12 = 0x0001   r13 = 0x7fc0f3e7a740
> r14 = 0xff92   r15 = 0x22217000
> rip = 0x7fdb5e2ffa82
> 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??
>
>
>

Re: Impala minidump dump_breakpad_symbols

2017-11-28 Thread sanysand...@gmail.com


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 = 0x7fd7d4fdf220   rsp = 0x7fc10d6ad270
 r8 = 0x7fd7d4fdf220r9 = 0x
r10 = 0x7fc10d6ad3d0   r11 = 0x0202
r12 = 0x0006   r13 = 0x7fc10d6ad3d0
r14 = 0xff92   r15 = 0x7fc10d6ad400
rip = 0x7fdb5e2ffa82
Found by: given as instruction pointer in context

Thread 960
 0  0x7fdb5e2ffa82
rax = 0xfdfc   rdx = 0x0001
rcx = 0x   rbx = 0x10d33e20
rsi = 0x0189   rdi = 0x10d33e4c
rbp = 0x7fc0f3e7a740   rsp = 0x7fc0f3e7a6b0
 r8 = 0x10d33e20r9 = 0x
r10 = 0x7fc0f3e7a740   r11 = 0x0202
r12 = 0x0001   r13 = 0x7fc0f3e7a740
r14 = 0xff92   r15 = 0x22217000
rip = 0x7fdb5e2ffa82
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/confluence/display/IMPALA/Building+Impala and also 
followed "build native-toolchain from scratch" 
https://cwiki.apache.org/confluence/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-1b704857f1e78a864e6942e613457e55f1aecb60-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??

Re: Impala minidump dump_breakpad_symbols

Re: Impala minidump dump_breakpad_symbols

[IMPALA-3060] Supports IS [NOT] NULL feature for complex types(e.g. STRUCT)

Re: Impala minidump dump_breakpad_symbols

Re: Impala minidump dump_breakpad_symbols

Re: Impala minidump dump_breakpad_symbols

Re: Impala minidump dump_breakpad_symbols

Re: Impala minidump dump_breakpad_symbols

Re: Protocol with re: to reverting previous patches

Re: Protocol with re: to reverting previous patches

Protocol with re: to reverting previous patches

Re: Impala minidump dump_breakpad_symbols

Re: Impala minidump dump_breakpad_symbols

Re: Impala minidump dump_breakpad_symbols

14 matches

Site Navigation

Mail list logo

Footer information