You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to enable source coverage output while fuzzing Hyperpill using Clang's source-based coverage. I followed the instructions from Discord and compiled L1 QEMU with the following configuration
export CC=clang export CXX=clang++ export CFLAGS="-fprofile-instr-generate -fcoverage-mapping" export CXXFLAGS="-fprofile-instr-generate -fcoverage-mapping" ./configure --target-list=x86_64-softmmu --enable-slirp --enable-sanitizers
I also set NOCOV=0 in scripts/run_hyperpill.sh. However, there is no coverage percentage output during fuzzing.
I have checked that Clang's coverage instrumentation should be enabled, but I am unsure if there are additional configurations required for Hyperpill to generate and display coverage data.
Could you provide any guidance on how to properly enable and retrieve coverage statistics while fuzzing Hyperpill?
The text was updated successfully, but these errors were encountered:
Hello Hyperpill team,
I am trying to enable source coverage output while fuzzing Hyperpill using Clang's source-based coverage. I followed the instructions from Discord and compiled L1 QEMU with the following configuration
export CC=clang export CXX=clang++ export CFLAGS="-fprofile-instr-generate -fcoverage-mapping" export CXXFLAGS="-fprofile-instr-generate -fcoverage-mapping" ./configure --target-list=x86_64-softmmu --enable-slirp --enable-sanitizers
I also set NOCOV=0 in scripts/run_hyperpill.sh. However, there is no coverage percentage output during fuzzing.
I have checked that Clang's coverage instrumentation should be enabled, but I am unsure if there are additional configurations required for Hyperpill to generate and display coverage data.
Could you provide any guidance on how to properly enable and retrieve coverage statistics while fuzzing Hyperpill?
The text was updated successfully, but these errors were encountered: