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
Crash while trying to read LLVM covmap #10
Comments
Thanks for filing this issue! I think I know what's happening (and unfortunately there is not much you can do to fix it as a user). Do you have a public repo I can use to reproduce it? If not, don't worry. (If you're comfortable with that, you can also email me the code so that it stays private) |
I was originally experimenting in a private project, but I also have a public one where the same error occurs: https://github.com/bailion/compiler/blob/main/logic/src/fuzzcheck/parse.rs. |
Thanks a lot. I will publish an update with the fix by the end of next week at the latest. |
I have just published fuzzcheck 0.7.1. Could you let me know if it resolves the issue or if you encounter other problems? Thanks. |
It fixes this issue (yay!) but I'm now getting a different error:
```
thread 'main' panicked at 'failed to properly link the different LLVM
coverage sections: CannotFindFunctionRecordAssociatedWithPrfData',
/Users/teymouraldridge/.cargo/registry/src/github.com-1ecc6299db9ec823/fuzzcheck-0.7.1/src/code_coverage_sensor/mod.rs:49:14
```
…On 09/08/2021 11:22, Loïc Lecrenier wrote:
I have just published fuzzcheck 0.7.1. Could you let me know if it
resolves the issue or if you encounter other problems? Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKFSTPIPXGVVMLM4BCOJDYLT36T5HANCNFSM5BWHQE7Q>.
|
argh, that's annoying. I thought that might happen, but I don't really understand it, so it might take longer to fix. [profile.release]
codegen-units = 1
lto = "thin" # maybe not necessary to your |
That got rid of that error, but another one has appeared
|
hm, that one is surprising. Thanks a lot for your help, I'll try and figure it out. I couldn't reproduce the issue on https://github.com/bailion/compiler/blob/main/logic/src/fuzzcheck/parse.rs . Does it also fail for you on that project? If not, do you have a public repo where the same error happens? |
Has that ever happened again? A few things have changed since then. I am going to close the issue in ~a week otherwise. |
I haven't encountered the issue since, although sometimes it crops up when calling |
right! I need to think about what should happen when Since |
That would make sense to me (example-based tests are definitely different to fuzzers in my mind) – Tarpaulin (xd009642/tarpaulin) also does something similar. |
I encountered this crash while trying to run
cargo-fuzzcheck
.This is using the
nightly-x86_64-apple-darwin
toolchain (rustc 1.56.0-nightly (b70888601 2021-07-28)
)I'm currently experimenting with different
rustc
versions to see if that makes a difference.I'm using the latest version of both
fuzzcheck
andcargo-fuzzcheck
(0.7.0)The command I'm using is
cargo fuzzcheck leaderboard::test::fuzz_id_encoding fuzz --artifacts fuzz/artifacts
(leaderboard::test::fuzz_id_encoding
is the path to the test)The text was updated successfully, but these errors were encountered: