Skip to content
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

Module not found "fuzzers.xxxxx" upon testing with new fuzzer #2063

Open
CowBoy4mH3LL opened this issue Jan 2, 2025 · 0 comments
Open

Module not found "fuzzers.xxxxx" upon testing with new fuzzer #2063

CowBoy4mH3LL opened this issue Jan 2, 2025 · 0 comments

Comments

@CowBoy4mH3LL
Copy link

I add a new fuzzer following instructions from https://google.github.io/fuzzbench/getting-started/adding-a-new-fuzzer/.
Basically, this new fuzzer directory (I call hfuzz_rb_afl) is a copy of aflplusplus_qemu.

If I try to test build the fuzzer

export FUZZER_NAME=hfuzz_rb_afl
cd fuzzbench_git_repo
source ./.venv/bin/activate
export PYTHONPATH=.
make -j4 build-$FUZZER_NAME-all

I get

 => ERROR [stage-1 15/15] RUN echo "Run fuzzer_build to build the target" && if [ -z "$debug_builder" ] ; then fuzzer_build; fi              4.0s
------                                                                                                                                            
 > importing cache manifest from gcr.io/fuzzbench/builders/hfuzz_rb_afl/bloaty_fuzz_target:                                                       
------                                                                                                                                            
------                                                                                                                                            
 > [stage-1 15/15] RUN echo "Run fuzzer_build to build the target" && if [ -z "$debug_builder" ] ; then fuzzer_build; fi:                         
1.145 Run fuzzer_build to build the target                                                                                                        
1.225 FUZZ_TARGET = fuzz_target
1.225 CFLAGS = -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION -pthread -Wl,--no-as-needed -Wl,-ldl -Wl,-lm -Wno-unused-command-line-argument -O3
1.225 CXXFLAGS = -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION -pthread -Wl,--no-as-needed -Wl,-ldl -Wl,-lm -Wno-unused-command-line-argument -stdlib=libc++ -O3
1.226 Traceback (most recent call last):
1.226   File "<string>", line 1, in <module>
1.226 ModuleNotFoundError: No module named 'fuzzers.hfuzz_rb_afl'
------

 3 warnings found (use --debug to expand):
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 26)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 27)
 - LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 28)
Dockerfile:66
--------------------
  64 |     
  65 |     COPY docker/benchmark-builder/fuzzer_build /usr/bin/fuzzer_build
  66 | >>> RUN echo "Run fuzzer_build to build the target" && if [ -z "$debug_builder" ] ; then fuzzer_build; fi
  67 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c echo \"Run fuzzer_build to build the target\" && if [ -z \"$debug_builder\" ] ; then fuzzer_build; fi" did not complete successfully: exit code: 1
make: *** [docker/generated.mk:36824: .hfuzz_rb_afl-bloaty_fuzz_target-builder] Error 1

Note that I do set the PYTHONPATH beforehand and execute the above in the venv.

Would really appreciate some help here :)

PS: I am completely local and this new dummy fuzzer is only for test, not to outsource as of yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant