-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Linking issue when building sample fuzzer #2
Comments
Thank you so much for the detailed bug report! I have looked at the issues you mentioned and it seems like I can use a workaround and keep the |
I think I fixed both issues :) The linker error is “fixed” by using the So in short, the tests are now compiled with two more options: I am sorry I did not test fuzzcheck on Linux before, I will add continuous integration tests with travis soon to make sure it always works in the future. Could you please verify that you can run the example now? Thanks! :) |
It works as expected now, thanks a lot for the fixes. I assume you usually test on macOS? |
Yes, I mostly test on macOS. I have a Linux docker container to test it on my machine now though, so I can test both easily :) |
Hi,
I ran into the following linking error while trying to build the sample fuzzer from the README.
My system:
There is an open ticket for similar error in cargo-fuzz, it seems to be apearing when compiling with optimizations.
rust-fuzz/cargo-fuzz#161
rust-lang/rust#53945
I did a test where I removed the
--release
flag in cargo-fuzz/main.rs, but then I get segfaults of child processes when trying to start the fuzzer.The text was updated successfully, but these errors were encountered: