Fabian Meumertzheim

@kjteske Happy to collaborate on LLVM patches that add versioned symbol support, it looks like this is indeed a blocker for adding Bazel support.

With Bazel 6, all Bazel `cc_*` rules define `BAZEL_CURRENT_REPOSITORY` to the name of the repository containing the target, which can be used for https://github.com/bazelbuild/bazel/issues/2160#issuecomment-487033719. Relying on it for https://github.com/bazelbuild/bazel/issues/2160#issue-192892490 would...

Based on my own experience with the rules_go and gazelle Bazel modules that mutually depend on each other, I can say that this case does work but can also be...

I don't see a problem with Gazelle depending on rules_license, both in WORKSPACE and MODULE.bazel land. A Gazelle extension sounds like exactly the right way to handle this with the...

Without any special support, you should be able to use `java_fuzz_test` with Scala dependencies as long as you can provide the Scala equivalent of the static `fuzzerTestOneInput` entry point. The...

We currently decode the byte array provided by libFuzzer in every execution, so I am a bit worried that switching out the highly optimized binary format for the fully reflection-based...

> I also haven't tested the performance and I didn't know that the encoding occurs in every iteration. This certainly wouldn't be great. We are looking into reusing the in-memory...

We will look into this and other ways to make the corpus entries easier to handle eventually. We are currently focusing on polishing the JUnit 5 based workflow though, so...

This shouldn't happen, but without reproduction steps it's difficult to assess the cause of this. Do you have an example you can share that demonstrates this issue?

Could you provide the steps that lead to that stack trace? How are you running fuzzing with your hook and how are you collecting coverage?