Skip to content
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

[bug] [undefined behaviour] Use of mem::uninitialized() #468

Closed
xacrimon opened this issue Feb 8, 2020 · 5 comments · Fixed by #474
Closed

[bug] [undefined behaviour] Use of mem::uninitialized() #468

xacrimon opened this issue Feb 8, 2020 · 5 comments · Fixed by #474

Comments

@xacrimon
Copy link

xacrimon commented Feb 8, 2020

Seems to occur in crossbeam-epoch.

Full MIRI output is here: https://github.com/xacrimon/dashmap/runs/433047062.
@cynecx
Copy link
Contributor

cynecx commented Feb 8, 2020

#458 should probably fix this.

@RalfJung
Copy link
Contributor

With rust-lang/rust#66059, this UB leads to a segfault. It would be great to get a fixed version of crossbeam-epoch released.

@RalfJung RalfJung mentioned this issue Feb 17, 2020
Merged
@xacrimon
Copy link
Author

@RalfJung according to @cynecx this should be fixed on master now. Care to try again?

@RalfJung
Copy link
Contributor

RalfJung commented Feb 17, 2020 •
edited
Loading

Yes it is fixed on master. But as far as I can see there's no release with the fix yet, so users are still affected.

@xacrimon
Copy link
Author

Alright. I will keep this issue open until a release is made.

This was referenced Feb 17, 2020
Closed
Merged
bors bot added a commit that referenced this issue Feb 17, 2020
@bors @jonhoo
Merge #474
556ebbc 
474: Patch release for all crossbeam crates. r=jeehoonkang a=jonhoo

This bumps the patch version for all sub-crates and the top-level crate and updates the changelogs with references to PRs where applicable. As far as I can tell, there are no breaking changes. The top-level crate has not change at all, though I bumped `rand` to `0.7` in all the crates, which I guess technically requires a patch bump if we do another release.

Fixes #473.
Closes #472.
Closes #468.
Closes #409.
Not sure if this also solves #347 by virtue of #458?

Co-authored-by: Jon Gjengset <jon@thesquareplanet.com>
bors bot added a commit that referenced this issue Feb 17, 2020
@bors @jonhoo
Merge #474
0210b05 
474: Patch release for all crossbeam crates. r=jeehoonkang a=jonhoo

This bumps the patch version for all sub-crates and the top-level crate and updates the changelogs with references to PRs where applicable. As far as I can tell, there are no breaking changes. The top-level crate has not change at all, though I bumped `rand` to `0.7` in all the crates, which I guess technically requires a patch bump if we do another release.

Fixes #473.
Closes #472.
Closes #468.
Closes #409.
Not sure if this also solves #347 by virtue of #458?

Co-authored-by: Jon Gjengset <jon@thesquareplanet.com>
@bors bors bot closed this as completed in #474 Feb 22, 2020
@bors bors bot closed this as completed in 6d6591a Feb 22, 2020
exrook pushed a commit to exrook/crossbeam that referenced this issue Oct 7, 2020
@chmanchester
Open files on worker threads rather than passing a file handle when h…
93475f3 
…ashing inputs. Fixes crossbeam-rs#468
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Patch release for all crossbeam crates. jonhoo/crossbeam
3 participants
@RalfJung @cynecx @xacrimon