valgrind: memory leak with query_modules
Module deinitialization is probably not called.
2015-02-19T18:35:04 info: shutting down
==18004==
==18004== HEAP SUMMARY:
==18004== in use at exit: 328 bytes in 2 blocks
==18004== total heap usage: 1,519 allocs, 1,517 frees, 6,292,833 bytes allocated
==18004==
==18004== 296 bytes in 1 blocks are definitely lost in loss record 2 of 2
==18004== at 0x4C29BCF: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==18004== by 0x50647B4: mm_alloc (mempattern.c:38)
==18004== by 0x154929: dnsproxy_load (dnsproxy.c:80)
==18004== by 0x1143BE: conf_process (conf.c:288)
==18004== by 0x115450: conf_open (conf.c:786)
==18004== by 0x112C2E: main (main.c:269)
==18004==
==18004== LEAK SUMMARY:
==18004== definitely lost: 296 bytes in 1 blocks
==18004== indirectly lost: 0 bytes in 0 blocks
==18004== possibly lost: 0 bytes in 0 blocks
==18004== still reachable: 32 bytes in 1 blocks
==18004== suppressed: 0 bytes in 0 blocks
==18004== Reachable blocks (those to which a pointer was found) are not shown.
==18004== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==18004==
==18004== For counts of detected and suppressed errors, rerun with: -v
==18004== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)