Using address sanitizer on darwin

1

Out of approximately 80 crates, two fails to build with RUSTFLAGS=-Zsanitizer=address. I get about 3 results on google when I search for "Interceptors are not working". Should I be doing something more than setting RUSTFLAGS=-Zsanitizer-address?

I tried setting export DYLD_INSERT_LIBRARIES=... in the terminal, but no difference.

==39627==ERROR: Interceptors are not working. This may be because AddressSanitizer is loaded too late (e.g. via dlopen). Please launch the executable with:
==39628==ERROR: Interceptors are not working. This may be because AddressSanitizer is loaded too late (e.g. via dlopen). Please launch the executable with:
DYLD_INSERT_LIBRARIES=/Users/niklasdusenlund/.rustup/toolchains/1.87.0-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc-stable_rt.asan.dylib
"interceptors not installed" && 0
DYLD_INSERT_LIBRARIES=/Users/niklasdusenlund/.rustup/toolchains/1.87.0-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc-stable_rt.asan.dylib
"interceptors not installed" && 0
error: could not compile `prost` (lib)

Caused by:
  process didn't exit successfully: `/Users/niklasdusenlund/.rustup/toolchains/1.87.0-aarch64-apple-darwin/bin/rustc --crate-name prost --edition=2021 /Users/niklasdusenlund/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/prost-0.13.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=172 --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C split-debuginfo=unpacked --cfg 'feature="derive"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "derive", "no-recursion-limit", "prost-derive", "std"))' -C metadata=43c4d3b68de541fe -C extra-filename=-2275d8bc251632e5 --out-dir /Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps -L dependency=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps --extern 'noprelude:alloc=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/liballoc-dd93ab5c38984109.rmeta' --extern bytes=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libbytes-75fbfbad5c31e880.rmeta --extern 'noprelude:compiler_builtins=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libcompiler_builtins-b757677c739bed6f.rmeta' --extern 'noprelude:core=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libcore-29bdb673044c6dfd.rmeta' --extern 'noprelude:panic_unwind=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libpanic_unwind-5acdb8dd041ba86d.rmeta' --extern 'noprelude:proc_macro=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libproc_macro-63f980506b7530e5.rmeta' --extern prost_derive=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libprost_derive-6d586cdf098b08cb.dylib --extern 'noprelude:std=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libstd-38410e73fa035e8d.rmeta' -Z unstable-options --cap-lints allow -Zsanitizer=address` (signal: 6, SIGABRT: process abort signal)
warning: build failed, waiting for other jobs to finish...
error: could not compile `zeroize` (lib)

Caused by:
  process didn't exit successfully: `/Users/niklasdusenlund/.rustup/toolchains/1.87.0-aarch64-apple-darwin/bin/rustc --crate-name zeroize --edition=2021 /Users/niklasdusenlund/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/zeroize-1.8.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=172 --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C split-debuginfo=unpacked --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 'feature="zeroize_derive"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("aarch64", "alloc", "default", "derive", "serde", "simd", "std", "zeroize_derive"))' -C metadata=0158f9fd23e668c5 -C extra-filename=-0563c42cb53388c1 --out-dir /Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps -L dependency=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps --extern 'noprelude:alloc=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/liballoc-dd93ab5c38984109.rmeta' --extern 'noprelude:compiler_builtins=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libcompiler_builtins-b757677c739bed6f.rmeta' --extern 'noprelude:core=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libcore-29bdb673044c6dfd.rmeta' --extern 'noprelude:panic_unwind=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libpanic_unwind-5acdb8dd041ba86d.rmeta' --extern 'noprelude:proc_macro=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libproc_macro-63f980506b7530e5.rmeta' --extern 'noprelude:std=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libstd-38410e73fa035e8d.rmeta' --extern zeroize_derive=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libzeroize_derive-14f513d216114154.dylib -Z unstable-options --cap-lints allow -Zsanitizer=address` (signal: 6, SIGABRT: process abort signal)

I'm also setting -Zbuild-std so that stdlibs are built with asan.

2

It's not clear what exactly your distinct, separate errors are. The way you've pasted them it looks like ASAN is running during the compilation step which causes compilation to fail. if you did export DYLD_INSERT_LIBRARIES="..." then re-ran your build command, don't do that. It would likely explain why the crates are failing to compile -- if the ASAN runtime library doesn't intercept the functions correctly then it will cause an abort, and your build commands are exiting with a SIGABRT.

At any rate, the interceptor error is caused by ASAN doing runtime hooking ("interceptors") of various functions (like memcpy, malloc, free, etc.) and when the ASAN runtime executes it checks to see if the hooks successfully applied.

The error is printed here: llvm-project/compiler-rt/lib/sanitizer_common/sanitizer_mac.cpp at db8cad0c8d00a691d1365e9b2962a7f2f4ff0890 · llvm/llvm-project · GitHub

It looks like you could set the ASAN_OPTIONS="verify_interceptors=0" env var to disable this check, but ASAN will likely not functionally work as expected. Why the interceptors are failing I'm unsure -- that's an ASAN runtime library issue though and not a Rust issue. The binary was linked correctly with ASAN and likely has ASAN instrumentation (verify with nm -gD <target_binary> | grep __asan).

3

Did you somehow build proc macros or build scripts with ASAN? As opposed to just the program? It kind of looks like it to me.

Another thing to try if that leads nowhere: can you reproduce on Linux (in a VM presumably)? I don't know much about Mac, so it could be worth checking if it is a Mac specific issue.

4

When I did this rustc borked majorly:

AddressSanitizer:DEADLYSIGNAL
=================================================================
==47601==ERROR: AddressSanitizer: BUS on unknown address (pc 0x000188c38124 bp 0x000170e39620 sp 0x000170e39620 T-1)
==47601==The signal is caused by a READ memory access.
==47601==Hint: this fault was caused by a dereference of a high value address (see register values below).  Disassemble the provided pc to learn which register was used.
    <empty stack>

==47601==Register values:
 x[0] = 0x0000600001b38000   x[1] = 0x0000000114e72438   x[2] = 0x0000000000000400   x[3] = 0x0000000000000014
 x[4] = 0x0000000000000000   x[5] = 0x0000000101044ba0   x[6] = 0x0000000000000000   x[7] = 0x00000000000000a2
 x[8] = 0x0000000000000001   x[9] = 0x0000000114e72438  x[10] = 0x0000000000000001  x[11] = 0x000000000000003f
x[12] = 0x0000000000000011  x[13] = 0x0000000000000000  x[14] = 0xffffffffffffe000  x[15] = 0xfffffffffffff000
x[16] = 0x0000000188c38124  x[17] = 0x000000000000d187  x[18] = 0x0000000000000000  x[19] = 0x0000000114e65370
x[20] = 0x0000000114e72438  x[21] = 0x000000010a9f0d10  x[22] = 0x000000010b2d06a8  x[23] = 0x0000000000000000
x[24] = 0x000000010b2d0930  x[25] = 0x00000000000000a0  x[26] = 0x0000000101e6ff00  x[27] = 0x0000000000000001
x[28] = 0x0000000101b75400     fp = 0x0000000170e39620     lr = 0x00000001111fc5ec     sp = 0x0000000170e39620
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: BUS
AddressSanitizer:DEADLYSIGNAL
AddressSanitizer: nested bug in the same thread, aborting.
error: could not compile `zeroize` (lib)

Caused by:
  process didn't exit successfully: `/Users/niklasdusenlund/.rustup/toolchains/nightly-aarch64-apple-darwin/bin/rustc --crate-name zeroize --edition=2021 /Users/niklasdusenlund/projects/shift/bitbox02-firmware/external/vendor/zeroize/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=172 --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 -C split-debuginfo=unpacked --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 'feature="zeroize_derive"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("aarch64", "alloc", "default", "derive", "serde", "std", "zeroize_derive"))' -C metadata=e252798443380819 -C extra-filename=-cdb46636a77abf40 --out-dir /Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps -L dependency=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps --extern zeroize_derive=/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/src/rust/fw/debug/deps/libzeroize_derive-f7b260d5c91eaaa1.dylib --cap-lints allow -Zsanitizer=address -L/Users/niklasdusenlund/projects/shift/bitbox02-firmware/build-build-noasan/lib --cfg=rust_secp_no_symbol_renaming` (exit status: 1)

This seems to be the case. I managed to reproduce it with a small sample app that depends on zeroize and enables derive feature.

But shouldn't rustc know not to build compiler plugins without asan?

I opened a bug report to get some more eyes on it: Building with address sanitizer on darwin aarch64 · Issue #146367 · rust-lang/rust · GitHub

edit:

Tried that and got

   Compiling zeroize v1.8.1 (/Users/niklasdusenlund/projects/niklas/utils/zeroize)
error[E0463]: can't find crate for `zeroize_derive`
   --> zeroize/src/lib.rs:246:9
    |
246 | pub use zeroize_derive::{Zeroize, ZeroizeOnDrop};
    |         ^^^^^^^^^^^^^^ can't find crate

error[E0432]: unresolved import `crate::Zeroize`
 --> zeroize/src/aarch64.rs:3:43
  |
3 | use crate::{atomic_fence, volatile_write, Zeroize};
  |                                           ^^^^^^^

edit2: maybe proc macros aren't supported?

5

That seems fairly broken yes. And it matches sanitizer - The Rust Unstable Book so presumably it should work.

Edit: Nope! Try passing --target explicitly as if you were cross compiling. I think that will fix it. But the diagnostics for this being needed is poor.

1 Like
6

YES! That solved it. Thank you so much for your help!

You might also need the --target

Would be helpful if the book mentions "when" you might need --target...

7

I think the compiler should give a useful error here. Rust does that in many other places. The current result is not a good user experience, and should really be improved before this is stabilised.

1 Like
8

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.