Open matthewkeil opened 6 months ago
The only solution I found was to save Jazzer deps as optional...
The only solution I found was to save Jazzer deps as optional...
We use yarn and this approach caused us issues downstream because yarn pulls optional and there is no flag to ignore them like there is for peer deps. We ended up just running an exec in the fuzz test entrance file if it was not installed yet.
We using the @jazzer/core for one of our libs which is also a native module. Thanks making this module!!! We prebuild the binaries for a number of architectures and found an edge case in your build process.
Issue 1) We are attempting to prebuild our library for linux/arm64 which is not prebuilt by jasser.js/fuzzer so it attempts to build it locally. The issue is that
prebuild
is adevDependency
.@jazzer.js/fuzzer
package.json
The installation falls back to the second case where
npm run prebuild
scripts runs and when it does it throwsError: prebuild not found
. Likely this is because its a dev dependency. For the time being we have addedprebuild
as a global package in our docker container but when the build runs we came up with the second issue below.Issue 2) Your
CmakeLists.txt
has a target that is not supported on linxu/arm64set(LIBFUZZER_TARGET "clang_rt.fuzzer_no_main-x86_64")
Not sure how to handle this second part of things but wanted to also bring it to your attention.