Thread safety of confd_connect() with cdb_connect()

[cohult]

Since you are using valgrind, make sure you have setup ConfD for valgrind use. See this post:

Valgrind "still reachable bytes" after API calls

From the ConfD UG Chapter “General Troubleshooting Strategies”: When debugging application memory leaks with a tool like valgrind, it is often necessary to rebuild libconfd from source, since the default build uses a “pool allocator” that makes the stack trace information for memory leaks from valgrind completely misleading for allocations from libconfd. The details of how to do a build that disables the pool allocator are described in the “Application debugging” section of the README in the l…