You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The source files pulled in from google/snappy make use of assert() for debugging, which are expected to be disabled in release builds when following their cmake build process by the presence of -DNDEBUG in the CXXFLAGS.
This flag is not specified for building those files as part of snappy-java. As a result, we discovered (due to a bug in our software) that it is possible to trigger failures of those assertions when using snappy-java, which terminates the process instead of propagating an exception back to Java code.
The text was updated successfully, but these errors were encountered:
The source files pulled in from google/snappy make use of assert() for debugging, which are expected to be disabled in release builds when following their cmake build process by the presence of -DNDEBUG in the CXXFLAGS.
This flag is not specified for building those files as part of snappy-java. As a result, we discovered (due to a bug in our software) that it is possible to trigger failures of those assertions when using snappy-java, which terminates the process instead of propagating an exception back to Java code.
The text was updated successfully, but these errors were encountered: