Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

JVM projects fail during introspector build due to incorrect $SRC path and coverage data is duplicated across multiple fuzzers #2220

Open
@leofernandesmo

Description

I've encountered two issues when running the introspector on JVM projects in OSS-Fuzz:

Issue 1: Build Failure Due to Incorrect $SRC Path
When executing (example) python infra/helper.py introspector apache-commons-jxpath, the build process fails with the following error:

++ basename -s .java /src/inspector/light/source_files/src/JXPathContextFuzzer.java
+ fuzzer_basename=JXPathContextFuzzer
+ javac -cp /out/commons-jxpath.jar::/usr/local/lib/jazzer_api_deploy.jar /src/inspector/light/source_files/src/JXPathContextFuzzer.java
+ cp /src/JXPathContextFuzzer.class /out/
cp: cannot stat '/src/JXPathContextFuzzer.class': No such file or directory
ERROR:__main__:Building fuzzers failed.

Root Cause analysis:

  • The introspector modifies the $SRC variable to point to /src/inspector/light/source_files/src/
  • However, the compiled .class files are being copied from the original $SRC path.
  • This creates a mismatch where the build script looks for .class files in the wrong location

Issue 2: Duplicate Coverage Data Across Multiple Fuzzers
When a project contains multiple fuzzers (2+), the introspector web interface displays identical coverage data for all fuzzers, rather than showing the individual coverage achieved by each fuzzer.

Expected Behavior: Each fuzzer should show its unique coverage data
Actual Behavior: All fuzzers display the same coverage metrics

Environment
OSS-Fuzz version: Latest (as of December 2024)
Project type: JVM projects
Test project: apache-commons-jxpath, metadata-extractor
Container: gcr.io/oss-fuzz-base/base-builder-jvm

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /