-
Notifications
You must be signed in to change notification settings - Fork 103
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
[question] Is this compilation failure due to the docker image's older rustc? Any way to update it? #105
Comments
Yeah, this is because the afl.rs Docker image is using a pinned version of rustc because of this issue. I haven't tried with a recent nightly, so maybe this problem no longer exists. I'm a bit busy for the next few days, so I won't have too much time to try a new rustc, but I'll try to get to it sometime. |
Thanks for the reply! I'll try dropping my dependency on |
And found 5 panicking test cases in as many minutes -- impressive! |
Oh, another thing that might be good to document in the README or the book somewhere: how to get Travis CI to test the exact rust nightly that afl.rs uses, so people maintaining libraries which they want to fuzz can retain the ability to compile under afl.rs's docker image. |
First off, thanks in advance for your time, and thanks for making afl.rs :)
When I try to use afl.rs with my C++ symbol demangling crate, which depends on
error-chain
, I get the following errors. I assume these are becauseserror-chain
depends on a newer rustc than the one bundled; is there a way to use a newer rustc with afl.rs?My normal rustc version (with which I can compile
error-chain
and my crate):The rustc in the docker image:
The logs when attempting to compile my crate and
error-chain
inside the docker image:The text was updated successfully, but these errors were encountered: