Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[openjpeg] Release cmake build type #5209

Merged
merged 1 commit into from
Feb 18, 2021
Merged

[openjpeg] Release cmake build type #5209

merged 1 commit into from
Feb 18, 2021

Commits on Feb 17, 2021

  1. [openjpeg] Release cmake build type 

    Seems that some bugs in openjpeg can be triggered only in release mode.
More specifically, I was trying to reproduce uclouvain/openjpeg#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.
    @andreafioraldi
    andreafioraldi authored Feb 17, 2021
    Configuration menu
    Copy the full SHA
    6433d21 View commit details
    Browse the repository at this point in the history