-
-
Notifications
You must be signed in to change notification settings - Fork 15k
Rust has no ASAN support for catalyst ABI (x86_64-apple-ios-macabi) #113935
Copy link
Copy link
Closed
Labels
A-sanitizersArea: Sanitizers for correctness and code qualityArea: Sanitizers for correctness and code qualityC-bugCategory: This is a bug.Category: This is a bug.O-iosOperating system: iOSOperating system: iOSO-macosOperating system: macOSOperating system: macOSO-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
Metadata
Metadata
Assignees
Labels
A-sanitizersArea: Sanitizers for correctness and code qualityArea: Sanitizers for correctness and code qualityC-bugCategory: This is a bug.Category: This is a bug.O-iosOperating system: iOSOperating system: iOSO-macosOperating system: macOSOperating system: macOSO-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)
Type
Fields
Give feedbackNo fields configured for issues without a type.
Building for
x86_64-apple-ios-macabiwith ASAN enabled produces this error:The
aarch64-apple-ios-macabitarget gives the same compiler error.Catalyst is a useful ABI for ASAN support because Chromium's iOS code is fuzzed on Catalyst, and ASAN is important to find bugs with fuzzers. This prevents us from having Rust code that is visible to Chrome's IOS product at all, or requires us to disable ASAN in the fuzzers.
Chromium issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1466967
For someone coming in without background in Rust's sanitizer support, what would be needed to bring up ASAN support for this ABI? Consider that we don't need a runtime from the stdlib at all, as we're using Clang's ASAN runtime.