-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICE dumps leak user names etc #128594
Comments
Pretty sure long ty names written to disk also has this issue |
making it a relative path would likely hurt usability, cargo sets the working directory to the crate source which is not necessarily the working directory of the user. it would be bad if they couldn't just copy paste the path and open it. |
Ah good point, in case a crate dependency causes the ICE, the backtrace file gets dumped into random dirs inside the We could probably fix 99% of the cases by checking if there is a something like a |
Could we replace a prefix matching the user's home dir with |
I think that we can likely use a combination of the above strategies. @yaahc just happens to be looking into making the target directory a user definable nightly config flag (instead of an env flag) so that |
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 reportThis 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
The text was updated successfully, but these errors were encountered: