Skip to content

Running sanitizer tests fails with mixed ABI errors #147394

Open
Open
Running sanitizer tests fails with mixed ABI errors#147394
Labels
A-ABIArea: Concerning the application binary interface (ABI)A-diagnosticsArea: Messages for errors, warnings, and lintsC-bugCategory: This is a bug.F-target_modifiers`#![feature(target_modifiers)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Description

@djc
djc
opened on Oct 6, 2025

I tried this code:

RUSTFLAGS="-Z sanitizer=address -Cunsafe-allow-abi-mismatch=sanitizer" cargo +nightly -Z build-std test --target x86_64-unknown-linux-gnu --all-features

I expected to see this happen: tests pass/fail

Instead, this happened:

error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `hashlink`
  |
  = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely
  = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=memory` in dependency `core`
  = help: set `-Zsanitizer=memory` in this crate or unset `-Zsanitizer` in `core`
  = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error

Note that I already added the suppression option, but it doesn't seem to take effect here?

Meta

rustc --version --verbose:

rustc 1.92.0-nightly (839222065 2025-10-05)

(See CI: https://app.circleci.com/pipelines/github/djc/hashlink/189/workflows/58588dc4-d323-428f-a309-d950c5fa2b0f/jobs/180.)

Activity

  1. saethlin
    added
    A-diagnosticsArea: Messages for errors, warnings, and lints
    A-ABIArea: Concerning the application binary interface (ABI)
    F-target_modifiers`#![feature(target_modifiers)]`
    and removed
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    -Zbuild-stdUnstable cargo option: -Zbuild-std
    on Oct 14, 2025
  2. rustbot
    added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Oct 14, 2025
  3. saethlin
    added
    A-diagnosticsArea: Messages for errors, warnings, and lints
    C-bugCategory: This is a bug.
    A-ABIArea: Concerning the application binary interface (ABI)
    F-target_modifiers`#![feature(target_modifiers)]`
    and removed
    A-diagnosticsArea: Messages for errors, warnings, and lints
    C-bugCategory: This is a bug.
    A-ABIArea: Concerning the application binary interface (ABI)
    F-target_modifiers`#![feature(target_modifiers)]`
    on Oct 14, 2025

  4. djc commented on Oct 15, 2025

    @djc
    djc
    on Oct 15, 2025
    ContributorAuthor

    @saethlin thanks a lot for digging in! This allowed me to make some progress.

    First, I still needed -Cunsafe-allow-abi-mismatch=sanitizer in RUSTFLAGS as well, otherwise it complained about build_script_build targets.

    Second, I'm now getting this error:

    error: failed to run custom build command for `compiler_builtins v0.1.160 (/home/circleci/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/compiler-builtins/compiler-builtins)`

Caused by:
  process didn't exit successfully: `/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build` (exit status: 1)
  --- stdout
  cargo::rerun-if-changed=build.rs
  cargo::rerun-if-changed=configure.rs

  --- stderr
  ==4238==WARNING: MemorySanitizer: use-of-uninitialized-value
      #0 0x55c19c2eee4f  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xe4e4f) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #1 0x55c19c2dec2d  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xd4c2d) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #2 0x55c19c2f289f  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xe889f) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #3 0x55c19c2cdc65  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xc3c65) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #4 0x55c19c2cd98a  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xc398a) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #5 0x55c19c3053df  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xfb3df) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #6 0x55c19c2cd94e  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xc394e) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #7 0x55c19c2e4cb6  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xdacb6) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)
      #8 0x7fbfa66a2d8f  (/lib/x86_64-linux-gnu/libc.so.6+0x29d8f) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d)
      #9 0x7fbfa66a2e3f  (/lib/x86_64-linux-gnu/libc.so.6+0x29e3f) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d)
      #10 0x55c19c255c84  (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0x4bc84) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81)

  SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/circleci/project/target/debug/build/compiler_builtins-9899e1b0fc09e9f4/build-script-build+0xe4e4f) (BuildId: 70be73c5757f295b1d4a95b89ef4ac1189242b81) 
  Exiting
warning: build failed, waiting for other jobs to finish...

    Is this worth an issue against compiler-builtins? Or maybe there is a suppression mechanism somewhere...

  5. saethlin commented on Oct 15, 2025

    @saethlin
    saethlin
    on Oct 15, 2025
    Member

    I led you astray. Using -Zbuild-std without --target makes Cargo rebuild the standard library but doesn't put it into cross-compilation mode, which leads to the RUSTFLAGS being applied to host builds (proc macros and build scripts) but they are still built against the precompiled sysroot.

    AddressSanitizer supports partially-instrumented builds, and MemorySanitizer does not. These false positives are the outcome, and there are handful of closed issues on the tracker of people filing bugs against the standard library because the toolchain let them misconfigure a build and get a report that looks like a true positive, but isn't. You are using -Cunsafe-allow-abi-mismatch to bypass the check that was written to prevent this situation :p

  6. djc commented on Oct 15, 2025

    @djc
    djc
    on Oct 15, 2025
    ContributorAuthor

    Thanks a lot! Was finally able to fix hashlink CI so we can get updates rolling again.

  7. Thomasdezeeuw commented on Oct 15, 2025

    @Thomasdezeeuw
    Thomasdezeeuw
    on Oct 15, 2025
    Contributor

    Seems like this is the same issue as #146465?

    Anyone looking for a quick fix using --all-targets skips the tests for docs, so:

    cargo test --all-targets -Z build-std --all-features --target $(TARGET)
  8. Thomasdezeeuw
    added 2 commits that reference this issue on Oct 15, 2025

    Don't run doc tests with sanitizer

    ad98174

    Don't run doc tests with sanitizer (#1908)

    d7873b2

  9. saethlin commented on Oct 15, 2025

    @saethlin
    saethlin
    on Oct 15, 2025
    Member

    Yes, if djc actually wants to run doctests, that would be #146465. I still think there is a diagnostic problem here, we shouldn't have diagnostics that lead to the confusion reported in the original issue description:

    Note that I already added the suppression option, but it doesn't seem to take effect here?

  10. gendx commented on Oct 22, 2025

    @gendx
    gendx
    on Oct 22, 2025
    Contributor

    Note that I already added the suppression option, but it doesn't seem to take effect here?

    If the error is about a doctest (not enough context to tell because the error message you pasted doesn't show the line at which the error occurs), you should add the suppression option to RUSTDOCFLAGS, not RUSTFLAGS. Perhaps that's where the confusion is coming from?

  11. saethlin commented on Oct 22, 2025

    @saethlin
    saethlin
    on Oct 22, 2025
    Member

    That has already been mentioned in #147394 (comment) but be aware that GitHub is hiding most of this thread because of the backlinks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-ABIArea: Concerning the application binary interface (ABI)A-diagnosticsArea: Messages for errors, warnings, and lintsC-bugCategory: This is a bug.F-target_modifiers`#![feature(target_modifiers)]`T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions