encrypted_batch
to nullptr
after delete. Avoid double free in the case of NDEBUG
.
encrypted_batch
to nullptr
after delete. Avoid double free in the case of NDEBUG
.
utACK fa462b365715928d2c6eb52ca6a448f367084f0f.
I wonder, though: Are we “explicitly” supporting running a binary compiled with NDEBUG
? If so, then we should probably not use assert(false)
in the two places here (and instead explicitly print an error message and exit using other means).
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.