You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2023/06/21 00:47:00 UTC
[jira] [Resolved] (IMPALA-12225) LLVM 5.0.1's ASAN cannot work with glibc >=2.34
[ https://issues.apache.org/jira/browse/IMPALA-12225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-12225.
------------------------------------
Fix Version/s: Impala 4.3.0
Resolution: Fixed
> LLVM 5.0.1's ASAN cannot work with glibc >=2.34
> -----------------------------------------------
>
> Key: IMPALA-12225
> URL: https://issues.apache.org/jira/browse/IMPALA-12225
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.3.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Critical
> Fix For: Impala 4.3.0
>
>
> On Redhat 9, the ASAN builds fail with:
> {noformat}
> ==97426==ERROR: AddressSanitizer failed to allocate 0x0 (0) bytes of SetAlternateSignalStack (error code: 22)
> {noformat}
> It is trying to run a binary that was produced out of the ASAN build (the binary is a tool used to generate other files to be built). It looks like this is related to this GCC Jira (which actually applies to the LLVM libasan code):
> [https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100114]
> It impacts glibc >=2.34, which covers Redhat 9 and Ubuntu 22.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org