ms-tob (Matt S)
- Login: ms-tob
- Registered on: 04/23/2024
- Last sign in: 04/23/2024
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 1 | 0 | 1 |
Activity
05/21/2024
-
11:17 AM Ruby Feature #20448: Make coverage event hooking C API public
- > 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...
05/17/2024
-
06:37 PM Ruby Feature #20448: Make coverage event hooking C API public
- **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...
05/01/2024
-
01:39 PM Ruby Feature #20448: Make coverage event hooking C API public
- 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. ...
04/24/2024
-
12:07 PM Ruby Feature #20448: Make coverage event hooking C API public
- > 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...
04/23/2024
-
05:55 PM Ruby Feature #20448 (Open): Make coverage event hooking C API public
- # 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...