mirror of https://github.com/google/oss-fuzz.git
f682792936
Seems that some bugs in openjpeg can be triggered only in release mode. More specifically, I was trying to reproduce https://github.com/uclouvain/openjpeg/issues/1228 using the OSS-Fuzz harness and I failed. I figured out that the bug is indeed reachable by the harness, but can be uncovered only in Release mode, otherwise, an assertion error blocks it. I guess that they use assertions only in Debug mode (WTF) and remove them in Release. So, IMO openjpeg should be fuzzed in Release mode as the configuration used in production is the one relevant for security. |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| build.sh | ||
| project.yaml | ||