Age | Commit message (Collapse) | Author |
|
Patch from rubiate. See #19999
|
|
|
|
|
|
|
|
|
|
Previously, you needed to store the previous log severity in a local
variable, and it wasn't clear if you were allowed to call these
functions more than once.
|
|
|
|
|
|
Part of 19999.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes ticket 19902; bugfix on 0.2.9.1-alpha; patch from rubiate
|
|
See changes file; closes ticket 20110.
|
|
|
|
Test-memwipe is *supposed* to invoke undefined behavior, alas.
Closes 20066.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Updating the consensus algorithm made a non-valid node never get
listed, which messed up some other tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
They use the same code as reporting assertion failures, so we should
invert the sense of what we're "asserting".
Fixes bug 20093.
|
|
We wanted to make sure -50 was a bad input, but instead we were
passing a 'min' that was greater than 'max'.
|
|
|
|
|
|
|
|
|
|
|
|
The functions it warns about are:
assert, memcmp, strcat, strcpy, sprintf, malloc, free, realloc,
strdup, strndup, calloc.
Also, fix a few lingering instances of these in the code. Use other
conventions to indicate _intended_ use of assert and
malloc/realloc/etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requires a recent version of chutney.
Also remove bridges+hs, as it's somewhat redundant.
|
|
|