mame (Yusuke Endoh) wrote in #note-7: > Thanks for the research. So, `TracePoint.new(:branch)` seems good enough for the use case of fuzzer, right? > ... Hi @mame, might I please request a review of the above PR? Or, what steps should ...ms-tob (Matt S)
Hi there, I finally got around to working on this idea: https://github.com/ruby/ruby/pull/16579 Let me know if there's any way I can aid in its review.ms-tob (Matt S)
> Thanks for the research. So, `TracePoint.new(:branch)` seems good enough for the use case of fuzzer, right? Yes, `TracePoint.new(:branch)` will work. It would be nice to have a C interface as well, but it's not strictly necessary. T...ms-tob (Matt S)
**TL;DR: I've been further researching how fuzzers gather coverage information, and what types of coverage are most useful for fuzzing. I think the best course of action regarding this request would be to implement a fairly general cover...ms-tob (Matt S)
Sorry for the delay, I've been considering different APIs and reevaluating Ruzzy's coverage collection. I think I've identified that Ruzzy's current coverage collection mechanism is flawed, so perhaps we should not use that as the goal. ...ms-tob (Matt S)
> I understand that what you need is a hook for LINE and BRANCH events. Am I correct? I just need a hook for BRANCH events. You can find that C extension code here: https://github.com/trailofbits/ruzzy/blob/v0.7.0/ext/cruzzy/cruzzy...ms-tob (Matt S)
# Abstract Gathering code coverage information is a well-known goal within software engineering. It is most commonly used to assess code coverage during automated testing. A lesser known use-case is coverage-guided fuzz testing, which...ms-tob (Matt S)
ms-tob (Matt S)12:46 PM Ruby Feature #20448: Make coverage event hooking C API public