-
Notifications
You must be signed in to change notification settings - Fork 107
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
Troubleshooting: linking with cc
failed
#141
Comments
cc
failedcc
failed
This looks like rust-lang/rust#53945 We may want to add this Rust flag temporarily as a workaround rust-fuzz/honggfuzz-rs@44167fe |
rust-fuzz#141 + rust-lang/rust#53945 track issues with linkage which regressed when rust updated to llvm 8. This commit adds a work around for such issues for cargo-afl. This helps with the ergonomics of cargo-afl, particularly for those less familiar with the project and the above issues. These changes can be safely removed once patches are landed in llvm and rust updates to use the patched version.
#141 + rust-lang/rust#53945 track issues with linkage which regressed when rust updated to llvm 8. This commit adds a work around for such issues for cargo-afl. This helps with the ergonomics of cargo-afl, particularly for those less familiar with the project and the above issues. These changes can be safely removed once patches are landed in llvm and rust updates to use the patched version.
a temporary fix was merged in #144 and just published in 0.4.2 |
I'm running into this exact same error when using AFL.rs 0.4.3, also on Arch Linux:
|
Indeed, it seems like crates relying on |
I also have a similar compile issue with
I also notice that I do not see the flags added in #144 listed during the linking. I can confirm that adding user-provided flags via $ export RUSTFLAGS="-Clink-arg=-fuse-ld=gold" does result in a successful build. I'm on Ubuntu 18.04, so it seems strange that this was not added automatically given this condition: Lines 193 to 199 in 0fbe9c5
|
The rust-fuzz#141 workaround was actually fully disabled because the OS condition was wrong. This fixes the workaround.
When the fix for rust-fuzz#141 is in effect if you pass extra RUSTFLAGS there is no space separating them and the command line breaks. Fix that by adding a space at the end of those flags, just like it's done in the common string.
The rust-fuzz#141 workaround was actually fully disabled because the OS condition was wrong. This fixes the workaround.
When the fix for rust-fuzz#141 is in effect if you pass extra RUSTFLAGS there is no space separating them and the command line breaks. Fix that by adding a space at the end of those flags, just like it's done in the common string.
The rust-fuzz#141 workaround was actually fully disabled because the OS condition was wrong. This fixes the workaround.
When the fix for rust-fuzz#141 is in effect if you pass extra RUSTFLAGS there is no space separating them and the command line breaks. Fix that by adding a space at the end of those flags, just like it's done in the common string.
The rust-fuzz#141 workaround was actually fully disabled because the OS condition was wrong. This fixes the workaround.
When the fix for rust-fuzz#141 is in effect if you pass extra RUSTFLAGS there is no space separating them and the command line breaks. Fix that by adding a space at the end of those flags, just like it's done in the common string.
Hey,
I wanted to try some basic rust fuzzing, following the tutorial, but
cargo afl build
fails. I have no idea how to start troubleshooting this, so I'd be thankful for any pointers. I'm just pastingfoo --version --verbose
output for a bunch of stuff that might be relevant.I'm on x86-64 Linux (arch linux), and there's a system-wide afl installation.
Gist of the error message (full output at the end of this issue)
/home/aljoscha/projects/rsssb/fuzz-legacy-msg/src/main.rs
cargo.toml
cargo afl --version
cargo --version --verbose
rustc --version --verbose
cc --version --verbose
ld --version --verbose
Error log of
cargo afl build --verbose
The text was updated successfully, but these errors were encountered: