dash/test/sanitizer_suppressions
MarcoFalke 3383b79049
Merge bitcoin/bitcoin#24312: addrman: Log too low compat value
fa097d074bc1afcc2a52976796bb618f7c6a68b3 addrman: Log too low compat value (MarcoFalke)

Pull request description:

  Before this patch, when writing a negative `lowest_compatible` value, it would be read as a positive value. For example `-32` will be read as `224`. There is generally nothing wrong with that. Though, similarly there shouldn't be anything wrong with refusing to read a negative value. I find the code after this patch more logical than before. Also, this allows dropping a file-wide sanitizer suppression.

  In practice none of this should ever happen. Bitcoin Core would never write a negative `lowest_compatible` in normal operation, unless the file storage is later corrupted by external influence.

ACKs for top commit:
  mzumsande:
    re-ACK fa097d074bc1afcc2a52976796bb618f7c6a68b3

Tree-SHA512: 9aae7b8fe666f52f667f149667025e0160cef1a793cc4d392e36608f65c2bee8096da429235118f40a3368f327aabe30f3732ae78c5874648ea6f423f2687b65
2024-11-17 17:49:40 -06:00
..
lsan Merge bitcoin/bitcoin#27362: test: remove GetRNGState lsan suppression 2024-10-23 18:57:24 -05:00
tsan Merge bitcoin/bitcoin#27661: doc, test: Document steps to reproduce TSan warning for libdb 2024-10-25 09:12:00 -05:00
ubsan Merge bitcoin/bitcoin#24312: addrman: Log too low compat value 2024-11-17 17:49:40 -06:00