about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2019-03-03 03:00:16 +0000
committerbors <bors@rust-lang.org>2019-03-03 03:00:16 +0000
commit7dbba3d03c5d3e9fdb96556eac1be49449c41edc (patch)
treeeda91750cfd2690b78e7198ec5166ec0aa5fb8b7 /src/libstd/sys/unix/stack_overflow.rs
parent0ea22717a1e01fa535534b85a5347a7e49fc79de (diff)
parentc0e8cf94103289c424c62ca48e1e3f56e352a84a (diff)
downloadrust-7dbba3d03c5d3e9fdb96556eac1be49449c41edc.tar.gz
rust-7dbba3d03c5d3e9fdb96556eac1be49449c41edc.zip
Auto merge of #58464 - jethrogb:jb/std-test-panic-output, r=alexcrichton
Use the correct stderr when testing libstd

When compiling the unit tests for libstd, there are two copies of `std` in existence, see [lib.rs](https://github.com/rust-lang/rust/blob/919cf42/src/libstd/lib.rs#L335-L341). This means there are two copies of everything, including thread local variable definitions. Before this PR, it's possible that libtest would configure a stderr sink in one of those copies, whereas the panic logic would inspect the sink in the other copy, resulting in libtest missing the relevant panic message. This PR makes sure that when testing, the panic logic always accesses the stderr sink from “realstd”, using the same logic that libtest uses.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions