-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
std: Don't cache stdio handles on Windows #40516
Conversation
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ |
📌 Commit af72b06 has been approved by |
🔒 Merge conflict |
This alters the stdio code on Windows to always call `GetStdHandle` whenever the stdio read/write functions are called as this allows us to track changes to the value over time (such as if a process calls `SetStdHandle` while it's running). Closes rust-lang#40490
af72b06
to
5ca8a73
Compare
@bors: r=aturon |
📌 Commit 5ca8a73 has been approved by |
⌛ Testing commit 5ca8a73 with merge b1d0e15... |
💔 Test failed - status-travis |
@bors: retry |
…uron std: Don't cache stdio handles on Windows This alters the stdio code on Windows to always call `GetStdHandle` whenever the stdio read/write functions are called as this allows us to track changes to the value over time (such as if a process calls `SetStdHandle` while it's running). Closes rust-lang#40490
⌛ Testing commit 5ca8a73 with merge d11f245... |
💔 Test failed - status-travis |
⌛ Testing commit 5ca8a73 with merge 25c8108... |
💔 Test failed - status-travis |
⌛ Testing commit 5ca8a73 with merge f4f9468... |
💔 Test failed - status-travis |
⌛ Testing commit 5ca8a73 with merge c65e7de... |
std: Don't cache stdio handles on Windows This alters the stdio code on Windows to always call `GetStdHandle` whenever the stdio read/write functions are called as this allows us to track changes to the value over time (such as if a process calls `SetStdHandle` while it's running). Closes #40490
💔 Test failed - status-appveyor |
… On Sun, Mar 26, 2017 at 2:37 PM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang/rust/build/1.0.2570>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40516 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95L7xpobTPOKTiRwcbsAEgD3AGmcRks5rpr5ngaJpZM4McsLJ>
.
|
⌛ Testing commit 5ca8a73 with merge 71123e4... |
std: Don't cache stdio handles on Windows This alters the stdio code on Windows to always call `GetStdHandle` whenever the stdio read/write functions are called as this allows us to track changes to the value over time (such as if a process calls `SetStdHandle` while it's running). Closes #40490
@bors retry |
…uron std: Don't cache stdio handles on Windows This alters the stdio code on Windows to always call `GetStdHandle` whenever the stdio read/write functions are called as this allows us to track changes to the value over time (such as if a process calls `SetStdHandle` while it's running). Closes rust-lang#40490
This alters the stdio code on Windows to always call
GetStdHandle
whenever thestdio read/write functions are called as this allows us to track changes to the
value over time (such as if a process calls
SetStdHandle
while it's running).Closes #40490