-
Notifications
You must be signed in to change notification settings - Fork 325
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
FFI implementation libc getuid on Linux #3753
Comments
We in fact already support The only hard part is a policy decision: currently it always returns 1000. Should we make it return the real ID instead? But what would that even mean when we run on a Windows host? |
Awesome!
I think for my purposes 1000 is sufficient. No need to over complicate it.
|
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Aug 10, 2024
allow all code to call getuid() Fixes rust-lang/miri#3753
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Aug 18, 2024
allow all code to call getuid() Fixes rust-lang/miri#3753
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I relatively often find code I want to run with Miri that depends on libc getuid when targeting linux. At least to my mind it is a basic operating system API worthy of a miri implementation that would enable more miri code coverage.
The text was updated successfully, but these errors were encountered: