this comment largely assumes you know how to create test harnesses to sanity check your code. from my experience, while glibc checks are useful, you need to kn

this comment largely assumes you know how to create test harnesses to sanity check your code. from my experience, while glibc checks are useful, you need to know about more cases such as overflows, overruns, races, etc. In my experience, I used valgrind withub a test harness to create the conditions i'd expect. The glibc approach doesn't seem to compete feature wise with valgrind. It seems to me that glibc bloat is caused by this. PS: I have ran valgrind in production, You just have to carefully canary it.