-
If I know that a particular region of code is leading to something potentially problematic, it seems like it would be good to add a mechanism to manually indicate that to AFL? I imagine the API would …
-
https://mp.weixin.qq.com/s/G26MJOH4VPene1Sd_zjEQw
-
Even though now all stateful tests are separate pytest items it might be better to run all of them in a single test function. Something like this:
```python
@schema.parametrize()
def test_api(cas…
-
In https://github.com/google/oss-fuzz/pull/4369
"Project tests / build (libfuzzer, coverage, x86_64) (pull_request)" fails.
But I don't even know why it is doing this build for that PR since the PR …
-
I'm doing some tests and afl-clang-fast seemed to ignore the `-fsanitize-coverage-allowlist` and `-fsanitize-coverage-blocklist` switches. However, the classic instrumentation mode did comply with the…
-
I think that `libFuzzer` whould be provided with Clang or LLVM, I am suprised not to find it anywhere in the Nix generated packages.
**Project description**
LibFuzzer is in-process, coverage-guide…
-
I ran AFL and it almost immediately produces a segmentation fault.
Can be reproduced by using the benchmark parse:
```
#0 find_structural_bits (buf=buf@entry=0x55555558f100 "\n", len=len@entry=1…
Yzoni updated
3 years ago
-
联合周报第 178 期开始投稿 :tada:
-
Do you think it makes sense to use https://github.com/jacoco/jacoco for coverage capturing?
-
I noticed that MemLock only optimizes seed selection based on coverage and memory comsumption. Why not changing other parts of the fuzzing loop? For example, seed mutation based on resource comsumptio…