It is very easy when using Glib to produce memory leaks (forgetting to unref some object).
It will be nice to create a CMake target test that runs Valgrind automatically on all the tests and fails if definitely lost or indirectly lost result values are different from 0.
Something like G_SLICE=always-malloc ; G_DEBUG=gc-friendly ; valgrind --leak-check=full --show-leak-kinds=all ./gconnman_clock_test
Currently, these values on all the tests return 0.
It is very easy when using Glib to produce memory leaks (forgetting to unref some object).
It will be nice to create a CMake target test that runs Valgrind automatically on all the tests and fails if
definitely lostorindirectly lostresult values are different from 0.Something like
G_SLICE=always-malloc ; G_DEBUG=gc-friendly ; valgrind --leak-check=full --show-leak-kinds=all ./gconnman_clock_testCurrently, these values on all the tests return 0.