Skip to content

spawn() results in valgrind warnings #14890

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

Closed
HildarTheDorf opened this issue Jun 14, 2014 · 2 comments
Closed

spawn() results in valgrind warnings #14890

HildarTheDorf opened this issue Jun 14, 2014 · 2 comments

Comments

@HildarTheDorf
Copy link

TaskBuilder::spawn() is causing a "conditional jump or move depends on uninitialized values(s)" error in valgrind.

fn main() { spawn(proc() {}) }
Is the absolute minimum required to reproduce, and the error message is still present if a TaskBuilder is created and TaskBuilder::spawn() is called directly. Tested on 18c451f (most recent master as of this post).

@thestinger
Copy link
Contributor

This is likely just the same false positive as #11710.

@HildarTheDorf
Copy link
Author

Looks like it. Sorry for the duplicate.

bors added a commit to rust-lang-ci/rust that referenced this issue Jun 5, 2023
use `::core` instead of `$crate` in `option_env!`

fix rust-lang#14885
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

No branches or pull requests

2 participants