Skip to content
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

RFC: Reading into uninitialized buffers #2930

Merged
merged 22 commits into from
Oct 28, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update text/0000-read-buf.md
Co-authored-by: Taiki Endo <te316e89@gmail.com>
  • Loading branch information
sfackler and taiki-e authored May 18, 2020
commit 9f498e3e2173fd79e575f50d9b9dbb7a92bc417c
2 changes: 1 addition & 1 deletion text/0000-read-buf.md
Original file line number Diff line number Diff line change
@@ -74,7 +74,7 @@ impl Read for BrokenReader2 {
In either case, the `process_data` call above would be working with uninitialized memory. Uninitialized memory is a
dangerous (and often misunderstood) beast. Uninitialized memory does not have an *arbitrary* value; it actually has an
*undefined* value. Undefined values can very quickly turn into undefined behavior. Check out
[Ralf's blog post](https://www.ralfj.de/blog/2019/07/14/uninit.html) for a more extensive discussion of unintialized
[Ralf's blog post](https://www.ralfj.de/blog/2019/07/14/uninit.html) for a more extensive discussion of uninitialized
memory.

## But how bad are undefined values really?