-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Some std::run tests fail under valgrind #7224
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
Comments
I'm curious about those error messages. Options: check if it's valgrind misconfigured for 32bit; try running valgrind in follow-children mode; strip LD_PRELOAD from subprocess env? |
Under valgrind on 64->32 cross compiles the dynamic linker is emitting some error messages on stderr, which interferes with the tests that are checking stderr.
@Aatch has a patch to remove LD_PRELOAD from the environment. |
Seems weird, no? What does fork-exec do under valgrind normally? |
No. They're "doing fine" because there's a sniff for valgrind that disables those checks. Not a fix, just a bandaid. |
Grep for |
Still a bug, doesn't seem like a release blocker. |
These tests where removed:
And this test seems to work just fine under valgrind:
|
Fix `redundant_closure` for `vec![]` macro in a closure with arguments fixes: rust-lang#7224 changelog: Fix `redundant_closure` for `vec![]` macro in a closure with arguments
Examples:
The problem is that they are checking the contents of stderr and the dynamic linker is writing it's own error messages there when running under valgrind.
The text was updated successfully, but these errors were encountered: