[
https://issues.apache.org/jira/browse/KUDU-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3089.
---------------------------------
Fix Version/s: 1.17.1
1.18.0
Resolution: Fixed
I could not reproduce the issue using Kudu built from source in the 1.17.x
branch (git hash e742f86f6d8e687dd02d9891f33e068477163016) on aarch64 machine
in ASAN configuration (Graviton3 instance in EC2), so I guess this isn't a
problem anymore. Feel free to reopen if it's still an issue.
I haven't done any RCA in this context, but I guess the issue has been
mitigated by upgrading LLVM/CLANG (and libunwind?) thirdparty components.
> ERROR when running tests on ARM64 server with TSAN or ASAN enabled
> ------------------------------------------------------------------
>
> Key: KUDU-3089
> URL: https://issues.apache.org/jira/browse/KUDU-3089
> Project: Kudu
> Issue Type: Bug
> Components: test
> Reporter: liusheng
> Priority: Major
> Fix For: 1.17.1, 1.18.0
>
>
>
> Fow now I am trying to build and test Kudu on ARM server, for Debug build
> type, the building process and almost all tests can pass. but for TSAN and
> ASAN building type, I can build sucessfully, but all the test cases will
> raise follow error.
> {code:java}
> root@kudu-asan2:/opt/kudu/build/asan# bin/kudu-ts-cli-test
> AddressSanitizer:DEADLYSIGNAL
> =================================================================
> ==14378==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc
> 0x000000000000 bp 0xffffc2649d10 sp 0xffffc2649d10 T0)
> ==14378==Hint: pc points to the zero page.
> ==14378==The signal is caused by a READ memory access.
> ==14378==Hint: address points to the zero page.AddressSanitizer can not
> provide additional info.
> SUMMARY: AddressSanitizer: SEGV (<unknown module>)
> ==14378==ABORTING
> {code}
> I have struggle for a while but no progress, could anyone help to give any
> suggestion ? thanks a lot!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
