huangtianhua created KUDU-3064:
----------------------------------
Summary: client_symbol-test failed on aarch64 server
Key: KUDU-3064
URL: https://issues.apache.org/jira/browse/KUDU-3064
Project: Kudu
Issue Type: Sub-task
Reporter: huangtianhua
I test kudu on aarch64 server based on https://gerrit.cloudera.org/#/c/14964/ ,
the test client_symbol-test failed, error info as below:
Found nm: /usr/bin/nm
Found kudu client library: ./../lib/exported/libkudu_client.so
Found bad symbol '_ULaarch64_dwarf_find_debug_frame'
Found bad symbol '_ULaarch64_dwarf_search_unwind_table'
Found bad symbol '_ULaarch64_get_reg'
Found bad symbol '_ULaarch64_init_local'
Found bad symbol '_ULaarch64_init_local2'
Found bad symbol '_ULaarch64_is_signal_frame'
Found bad symbol '_ULaarch64_resume'
Found bad symbol '_ULaarch64_step'
Found bad symbol '_Uaarch64_flush_cache'
Found bad symbol '_Uaarch64_get_accessors'
Found bad symbol '_Uaarch64_get_elf_image'
Found bad symbol '_Uaarch64_get_exe_image_path'
Found bad symbol '_Uaarch64_is_fpreg'
......
Kudu client library contains 13 bad symbols
I executed `nm` manually on x86 then, and found that there are symbol of
libunwind code are different with aarch64, like:
on aarch64:
00000000004d8fb8 T _ULaarch64_get_reg
/opt/kudu/thirdparty/src/libunwind-1.3.1/src/mi/Gget_reg.c:29
on x86_64:
00000000004c60e0 t _ULx86_64_get_reg
/opt/kudu/thirdparty/src/libunwind-1.3.1/src/mi/Gget_reg.c:29
I am not familar with this scope, but seems the logic of client-symbol_test.sh
should be modified for aarch64 to avoid bad symbols?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
