Tracking Issue for stabilizing the sanitizers (e.g., AddressSanitizer, LeakSanitizer, MemorySanitizer, ThreadSanitizer)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for stabilizing the sanitizers (e.g., AddressSanitizer, LeakSanitizer, MemorySanitizer, ThreadSanitizer). The original tracking issue for the sanitizers support for Rust is #39699. This is part of our work to organize and stabilize support for the sanitizers. (See our roadmap at https://hackmd.io/@rcvalle/S1Ou9K6H6.)
Steps
- Add support for separating sanitizers support in stable and unstable for supported targets.
- Stabilize AddressSanitizer and LeakSanitizer for Tier 1 targets.
- Create new Tier 2 targets with sanitizers enabled by default.
- Stabilize AddressSanitizer for the new Tier 2 targets.
- Stabilize MemorySanitizer and ThreadSanitizer for the new Tier 2 targets.
Unresolved Questions
Is there any concern or anything that the community would like to see implemented before their stabilization?
Implementation history
- #123617
- https://github.com/rust-lang/rust-project-goals/pull/337
- https://github.com/rust-lang/rust-project-goals/blob/main/src/2025h2/stabilization-of-sanitizer-support.md
- https://github.com/rust-lang/rust-project-goals/issues/403
- https://github.com/rust-lang/rust-project-goals/blob/main/src/2026/stabilization-of-sanitizer-support.md
- https://github.com/rust-lang/compiler-team/issues/943
- https://github.com/rust-lang/compiler-team/issues/951
- #149644
- #152757
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the stabilization guide, the sanitizer roadmap, and the linked implementation history, including #123617 and the project-goals documents. This is a coordination issue rather than a self-contained code task; done means resolving the checklist items and addressing concerns before stabilizing sanitizer support for the listed targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100