Thanks!
Could you please add a PR description explaining the goal of the PR? We already have tests of the file system APIs and if read did not initialize the buffer they would obviously fail.
It would be nice to have some tests that check the libc APIs (open/read/write/close) directly, basically a libc version of src/shims/unix/fs.rs -- see https://github.com/rust-lang/miri/issues/3179. If that is the goal of this PR then the filename and test content should be adjusted accordingly. Specifically, this should be added in tests/pass-dep/shims/libc-fs.rs (after checking that none of the existing tests there already covers this).
Thanks! Could you please add a PR description explaining the goal of the PR? We already have tests of the file system APIs and if
read
did not initialize the buffer they would obviously fail.It would be nice to have some tests that check the libc APIs (open/read/write/close) directly, basically a libc version of
src/shims/unix/fs.rs
-- see https://github.com/rust-lang/miri/issues/3179. If that is the goal of this PR then the filename and test content should be adjusted accordingly. Specifically, this should be added intests/pass-dep/shims/libc-fs.rs
(after checking that none of the existing tests there already covers this).