-
Notifications
You must be signed in to change notification settings - Fork 98
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
Invalid path reported for Rust toolchain #2681
Comments
Replicating this issue in a ubuntu environment, gave this response -
What this tells me is that, the path to the toolchain is being hardcoded from where the binary is being built. In this case, in the |
I believe this is related to this PR: #976. More specifically, this change: https://github.com/model-checking/kani/pull/976/files#diff-ad7f3edc0c2f338653896927f634fc2b24a45720db4249bda577be21bb9fabb5 See this comment in the PR:
One side effect of reverting this change, is that Kani will always display invalid path for toolchain files. This could impact the VSCode extension (if it uses the paths printed by Kani) and it will impact the visualize trace which probably won't display the contents of standard library functions. If we do want to make sure the path points to the local version of the rust toolchain, we will likely need to build all our libraries locally as part of the setup process. |
I think I'm having the same issue here. I'm trying to run a basic harness that imports a struct with a lot of dependencies. I run it with
I'm wondering how can I debug my code to see the conflicting steps. I've already used Any clues? |
Hi @fedejinich ! What version of Kani are you running, and do you have a harness that would allow us to reproduce your error? |
Hi @fedejinich, if I remember correctly, the remap option has to be done on the release bundle side. For now, you should be able to find the files by manually replacing the |
I got this error:
But I don't understand why it says "/Users/ec2-user/". I don't have this user on my machine! :)
Originally posted by @ithinkicancode in #2423 (comment)
The text was updated successfully, but these errors were encountered: