-
Notifications
You must be signed in to change notification settings - Fork 349
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
cargo-miri has problems with spaces in sysroot #705
Comments
Interesting. I can reproduce this locally without Miri being involved -- the issue is in xargo or further upstream:
Actually, it's a cargo issue: rust-lang/cargo#6139 |
Also see this xargo issue: japaric/xargo#206 |
109: Use some ptr::addr_of_mut for taking ptr addr r=lnicola a=CAD97 Relevant to #108, but I'm not certain if it addresses the miri failure or not. (Can't check because of rust-lang/miri#705.) Either way, this is a positive change, as previously we were creating `&mut` to uninitialized memory locations. Co-authored-by: Durham, Christopher <cdurham@smu.edu>
The xargo issue got fixed by japaric/xargo#336. Could someone who was affected by this problem try installing the most recent xargo ( |
I've installed miri via
rustup add component miri
When trying to run a hello world crate via miri, I get the following output:
It seems that either xargo or miri is handling the sysroot wrong and splits the sysroot by spaces, so it doesn't find the sysroot if the path contains spaces:
should be a single argument:
The text was updated successfully, but these errors were encountered: