-
### Component
Forge
### Describe the feature you would like
Currently, the forge fuzz testing and invariant testing don’t support coverage-guided fuzzing, which could generally improve the fuzzing …
-
Part of what makes afl-fuzz and libfuzzer so effective is their branch coverage feedback loop. Most of theft's heuristics are focused on shrinking failures it finds, but until it finds a failure, it's…
-
This issue tracks the release notes text for #131829.
### Steps
- [x] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review …
-
Hi,
There's https://github.com/rohanpadhye/jqf by @rohanpadhye
The idea here is that a randomized-input generation can be guided based on the feedback from the test execution.
For instance, gui…
-
I noticed that while debugging the https://rustc-dev-guide.rust-lang.org/ documentation that utilizes `-f` option for files modified against the master branch.
The problematic invocation:
```
❯ R…
-
**Is your feature request related to a problem? Please describe.**
I know that I can use libcc to instrument a C program but I am not sure how to instrument a Rust program and get the coverage data.
…
-
I input an unpublished reference assembly to stringtie with the -G option . The reference gtf has no UTR data; the transcript boundaries in every case are coterminous with the 5' and 3' coordinates of…
-
LSTS syntax is a lot nicer to read and maintain.
-
Right now, every Raw Gadget endpoint read/write ioctl submits a USB request and waits until its completion. This is done deliberately to assist with coverage-guided fuzzing by having a single syscall …
xairy updated
3 weeks ago
-
Hello
I'm following the Readme guide, and when i'm running "make" in GuidedSampler it's exiting with error 1.
```
─$ make
g++ -g -O3 -o guidedsampler guidedsampler.cpp -lz3
/usr/bin/ld: /…