Skip to content

lock_held_by_current_thread is probably not threadsafe #1186

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Nov 18, 2011 · 1 comment
Closed

lock_held_by_current_thread is probably not threadsafe #1186

brson opened this issue Nov 18, 2011 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Milestone
0.2 release, deta...

Comments

@brson
Copy link
Contributor

brson commented Nov 18, 2011

helgrind is suspicious of this function and I very infrequently see assertion failures involving it on codepaths that don't look like they could be failing.
@brson
Copy link
Contributor Author

brson commented Feb 2, 2012

Fixed by f76e6c3

@brson brson closed this as completed Feb 2, 2012
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
@rrbutani
Remove a dead link in new-target.md + other nits (rust-lang#1186)
1332fc7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Milestone
0.2 release, detail work, cleanup and...
Development

No branches or pull requests
1 participant
@brson