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
tools/oss-fuzz.sh doesn't seem to be working on systems where libFuzzer is a builtin sanitizer #10645
Labels
Comments
evverx
added
bug 🐛
Programming errors, that need preferential fixing
build-system
labels
Nov 5, 2018
Judging by google/oss-fuzz#2312 (comment), |
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 18, 2019
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 18, 2019
evverx
added a commit
to evverx/systemd
that referenced
this issue
Apr 18, 2019
evverx
added a commit
to evverx/systemd
that referenced
this issue
May 8, 2019
evverx
added a commit
to evverx/systemd
that referenced
this issue
May 9, 2019
edevolder
pushed a commit
to edevolder/systemd
that referenced
this issue
Jun 26, 2019
Yamakuzure
pushed a commit
to elogind/elogind
that referenced
this issue
Sep 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it would make sense to try compiling something like
with
-fsanitize=fuzzer
to check whetherclang
is new enough to support that.That's not critical as long as
libFuzzer
is built as a static library by the OSS-Fuzz project for, I presume, backwards compatibility, but it would certainly make the script a little bit more useful for people who, for some reason, want to build the fuzzers without theDocker
machinery.The text was updated successfully, but these errors were encountered: