-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
comm::recv() problem #4002
Comments
In addition, I'm now using the 0.5 version rustc. |
Can you provide example code? This bug is too vague as filed. |
Closing due to lack of clarification. @Aydin-Kim , please file a new bug if you can provide a small amount of code that provokes an error. |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Sep 28, 2021
Fix various redundant_closure bugs changelog: Fix various false negatives and false positives for [`redundant_closure`] Closes rust-lang#3071 Closes rust-lang#4002 This lint is full of weird nuances and this is basically a re-write to tighten up the logic.
RalfJung
added a commit
to RalfJung/rust
that referenced
this issue
Nov 21, 2024
Remove MutexID list
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm now doing a http_client work.
It seems there is a problem within comm::recv(port) module.
If I run the comm::recv(port), task fail is always occurs with this message
"*** stack smashing detected ***"
The text was updated successfully, but these errors were encountered: