bson_valgrind3
Use valgrind to check for bson data leaks a stack-allocated bson_t contains a small internal buffer; it only heap-allocates additional storage if necessary, depending on its data size. therefore if you forget to call bson_destroy() on a stack-allocated bson_t, it might or might not cause a leak that can be detected by valgrind during testing. to catch all potential bson data leaks in your code, configure the bson_memcheck flag: with this flag set, every bson_t mallocs at least one byte. run your program's unittests with valgrind to verify all bson_t structs are destroyed. set the environment variable mongoc_test_valgrind to on to skip timing-dependent tests known to fail with valgrind.
Releases
3 releases since Debian 10 (Buster); the text changed 2 times.