-
Notifications
You must be signed in to change notification settings - Fork 23
Valgrind
gtoubassi edited this page Mar 29, 2011
·
2 revisions
Memory error checking in the c++ implementation is done by running the unit tests or fzip through valgrind. Currently favored command line:
valgrind --leak-check=full --show-reachable=yes --dsymutil=yes ./fztests
Currently some invalid reads show up in deflate, and googling indicates this is known and not a bug but an optimization. Haven't investigated deeply.
Also a few bits of reachable memory allocated by libc, usually related to streams, vsprintf, and cout. I believe these are allocations of shared/pooled buffers which will never get freed.