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
include libFuzzer in the NDK #305
Comments
@DanAlbert |
No, it is not. We are hoping to have it in r16, but it could be later than that depending on other bugs. |
@stephenhines: I forget where we landed on this. Is this going to require moving the NDK's libc++ into the toolchain? |
Yes, all of libc++ will have to live inside the toolchain if we want to do anything like this. That is the cost of shipping "prebuilts". |
Yeah, I'm afraid that's a pretty big change on our end that will probably hinder development quite a bit (and this is the worst possible time to hinder our libc++ work), so this is going to have to go on the back burner until we're in a different position. |
so , it's impossible to use libfuzzer to test Android for now |
Out of the box, yes. I think you could fetch the LLVM sources matching the NDK compiler release (the SVN revision is in AndroidVersion.txt) and build your own libFuzzer with the NDK and use it. In fact, this is probably a better choice for us than trying to move libc++ into the toolchain. @stephenhines, do you see any issues with that? |
That should mostly work for a dedicated developer. We do occasionally have other patches on top of that SVN revision, but I don't think I have ever seen one that would impact libFuzzer. Ultimately we do need to move libc++ into the toolchain to support many other prebuilts, but right now, I think this is the most timely option. |
@stephenhines @DanAlbert |
well, there comes the problem. |
r15's Clang should. |
@DanAlbert |
Yeah, we know. It's the main priority and has been for a few releases, but other things keep getting in the way. |
Apparently I opened this bug twice. The fuzzer works now. Not sure when it was first supported, but there's a working example in #653 |
Including LLVM's libFuzzer in the NDK would make it easier for developers to track down odd crashes that they see reported in the field but can't reproduce locally.
The text was updated successfully, but these errors were encountered: