ICE dumps leak user names etc
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
When you trigger an ICE, rustc generates this stacktrace file and prints its location as absolute path:
note: please attach the file at /home/matthias/vcs/github/rust/rustc-ice-2024-08-03T09_07_05-3443169.txt to your bug report
This absolute path is part of the backtrace and often copied into the ticket and can contain sensitive information such as users real names or where they work, when its a work computer, etc...
Can we make this a relative path?
cc @estebank
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 by tracing rustc's ICE stacktrace-file generation and the code that prints the attachment note, reproducing the /home/... path shown in the issue. Done means the diagnostic no longer exposes a user's absolute path while still identifying the generated file for bug reports, with relevant compiler tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100