diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2016-01-30 17:57:17 +0530 |
|---|---|---|
| committer | Manish Goregaokar <manishsmail@gmail.com> | 2016-01-30 17:57:17 +0530 |
| commit | e31f65b010267c1796ee9ba1bb705b355b9c6691 (patch) | |
| tree | 98e4c1a93768b5d30e6077c92e38e1ebd000f9a8 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 5ff52dbf2ffdde50a126c4ad1a2da2cebbba317a (diff) | |
| parent | b960de0984cec27989746eec6fa706b3a7b46ad3 (diff) | |
| download | rust-e31f65b010267c1796ee9ba1bb705b355b9c6691.tar.gz rust-e31f65b010267c1796ee9ba1bb705b355b9c6691.zip | |
Rollup merge of #31292 - alexcrichton:osx-dtors-in-dtors-in-dtors, r=aturon
This test has been deadlocking and causing problems on the bots basically since its inception. Some memory safety issues were fixed in 987dc84b, but the deadlocks remained afterwards unfortunately. After some investigation, I've concluded that this is just a situation where OSX is not guaranteed to run destructors. The fix in 987dc84b observed that OSX was rewriting the backing TLS memory to its initial state during destruction while we weren't looking, and this would have the effect of canceling the destructors of any other initialized TLS slots. While very difficult to pin down, this is basically what I assume is happening here, so there doesn't seem to really be anythig we can do to ensure the test robustly passes on OSX, so just ignore it for now.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
