Skip to content

rustuv: Don't zero-out data on clones #15252

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

Merged
merged 1 commit into from
Jun 29, 2014
Merged

Conversation

alexcrichton
Copy link
Member

When cloning a stream, the data is already guaranteed to be in a consistent
state, so there's no need to perform a zeroing. This prevents segfaults as seen
in #15231

Closes #15231

When cloning a stream, the data is already guaranteed to be in a consistent
state, so there's no need to perform a zeroing. This prevents segfaults as seen
in rust-lang#15231

Closes rust-lang#15231
bors added a commit that referenced this pull request Jun 29, 2014
When cloning a stream, the data is already guaranteed to be in a consistent
state, so there's no need to perform a zeroing. This prevents segfaults as seen
in #15231

Closes #15231
@bors bors closed this Jun 29, 2014
@bors bors merged commit ca7fb82 into rust-lang:master Jun 29, 2014
@alexcrichton alexcrichton deleted the issue-15231 branch June 30, 2014 14:36
bors added a commit to rust-lang-ci/rust that referenced this pull request Jul 17, 2023
… r=lnicola

editor/code: Enable TypeScript's `--useUnknownInCatchVariables` option

This enables TypeScript's [`--useUnknownInCatchVariables`](https://www.typescriptlang.org/tsconfig#useUnknownInCatchVariables).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Race condition causes segfault in librustuv when using libgreen with stream reading
3 participants