"in use at exit: 0 bytes" is not portable
awilfox opened this issue · comments
Dynamic linking is leaky on Darwin and Linux/musl.
Using file I/O is leaky on Solaris.
These leaks are known to Valgrind and will correctly show "still reachable: 0 bytes in 0 blocks"; however, the Heap Summary includes suppressions. This causes FC-Solver (and others, I'm sure) to fail tests on musl et al due to, for example: "in use at exit: 782 bytes in 2 blocks" from the "board_gen -t only" test.
My suggestion would personally be to use "still reachable: 0 bytes" in addition to "in use at exit: 0 bytes". However, I'm not sure if you may have a better idea.
Thanks for the report - I'll think about it.