-
Notifications
You must be signed in to change notification settings - Fork 19
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
UB from a crater run #27
Comments
Hey, thanks for the bug report. I wonder if this issue isn't related to a symlink handling bug discovered in #23 |
I don't think that would be possible. |
Dang that's unfortunate. I'm not sure what I can do to fix this without a test case :( |
Closing this issue do not having possible solution merged and no replicable test case. |
@darakian I think this is a bug in crossbeam-epoch; the crate seems to depend on v0.7.1. v0.7.2 fixes a critical bug. I am wondering why that version was not picked automatically? crossbeam-epoch is a transitive dependency it seems. (Btw, the relevant rustc change here is rust-lang/rust#71274.) |
The dependency seems to be via rayon. But that doesn't explain why it did not use v0.7.2. Crater has been testing ddh-0.10.9; unfortunately there seem to be no tags in this repository so I cannot easily look at the code as it was back then. |
@RalfJung Thanks for the follow up and sorry about the lack of tags. The dependencies at the time of
Is it just Here's a link to the repo on |
0.10.9 was the latest version at the time the test was run, so I cannot say if newer versions still show this problem. In your local lockfile, which version of crossbeam-epoch does it use? |
Looks like
|
Okay. I think we can consider this issue resolved then, and the next time around crater should pick up the latest version of crossbeam-epoch I hope. |
🤞 Thanks again for reaching out :) |
I got a panic from a crater run which included this crate (in case you are not aware, crater is a tool that runs rustc against a set number of locked crates to check for regressions). It was with 0.10.9 version so i'm not sure if it still holds true in the 0.11.0 or not. Also, it could be caused by one of the dependencies. I tried tracking it down but I couldn't find anything.
The main point of the crater run was to find UB according to this advisory: rustsec/advisory-db#298.
Edit: there is a small possibility that this could be due to the file permissions being denied in crater runs
The crater output is:
The text was updated successfully, but these errors were encountered: