DavidKorczynski

> Ops, lint failure : ) I'll keep it a draft for just a bit, will fix the CI before making it ready :)

With the changes in https://github.com/ossf/fuzz-introspector/pull/684 the logging output I get from a OSS-Fuzz run is the following: ``` Running introspector frontend on ASCIIUtilityFuzzer.class :: {'ASCIIUtilityFuzzer.jar', 'BASE64EncoderStreamFuzzer.jar', 'angus-core.jar'} Running command: [java...

I can confirm it works following https://github.com/ossf/fuzz-introspector/pull/688 as well as removing the necessary `com.sun.` exclusion prefix from https://github.com/ossf/fuzz-introspector/blob/a3c1037b0e25824c86c866538c5e85cc908ff590/frontends/java/oss-fuzz-main.py#L107 Screenshot: 

Is this solved @arthurscchan ?

This sounds great! Let me go a bit more over this and assist with scoping out for Rust. See [LanguageImplementation](https://github.com/ossf/fuzz-introspector/blob/main/doc/LanguageImplementation.md) for details on how to add a new language. Rust...

In terms of control flow, then ideally because Rust is based on LLVM we could do the analysis directly on LLVM IR and use the logic from https://github.com/ossf/fuzz-introspector/tree/main/frontends/llvm to do...

it's often easier to go by way of Monorail when searching issues for a given project. For example, the following query should give you the issues for Skia: https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj%3Dskia&can=2 You...

> There was also some mention some place of moving the fuzzing code itself into this repo so that we could extend it. How do we make that happen? Move...

> @DavidKorczynski I think it's probably somewhat related to [ossf/fuzz-introspector#734](https://github.com/ossf/fuzz-introspector/issues/734) in the sense that it's another example of where diffs between two reports can be used. Interesting, thanks for pointing...

> note that you can also use honggfuzz with non-persistent targets, afl++ is not the only option. I think we should go for this too then