Hi Patrick, Running the latest code 1.29. I simply ran a valgrind(as I am learning this tool) on connmanctl, and got some leaks in it. Can you please verify or suggest something on validity of these leaks ?
My System is a Ubuntu 14.10 with 3.16.0-23-generic ubuntu kernel. //-----------------------------------Connmanctl Valgrind Output-------------------------------------// connmanctl> quit ==5716== ==5716== HEAP SUMMARY: ==5716== in use at exit: 129,221 bytes in 330 blocks ==5716== total heap usage: 646 allocs, 316 frees, 151,373 bytes allocated ==5716== ==5716== Searching for pointers to 330 not-freed blocks ==5716== Checked 236,704 bytes ==5716== ==5716== 19 bytes in 2 blocks are definitely lost in loss record 33 of 163 ==5716== at 0x4C2ABA0: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5716== by 0x53C2288: xmalloc (in /lib/x86_64-linux-gnu/libreadline.so.6.3) ==5716== by 0x53A14F6: readline_internal_teardown (in /lib/x86_64-linux-gnu/libreadline.so.6.3) ==5716== by 0x53B869E: rl_callback_read_char (in /lib/x86_64-linux-gnu/libreadline.so.6.3) ==5716== by 0x409CFD: input_handler (in /usr/local/bin/connmanctl) ==5716== by 0x50C8B6C: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1) ==5716== by 0x50C8F47: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1) ==5716== by 0x50C9271: g_main_loop_run (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1) ==5716== by 0x40A0EA: __connmanctl_input_init (in /usr/local/bin/connmanctl) ==5716== by 0x55F5EC4: (below main) (libc-start.c:287) ==5716== ==5716== 144 (72 direct, 72 indirect) bytes in 1 blocks are definitely lost in loss record 109 of 163 ==5716== at 0x4C2CC90: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5716== by 0x4E54FE7: ??? (in /lib/x86_64-linux-gnu/libdbus-1.so.3.8.7) ==5716== by 0x4E44C9E: dbus_connection_send_with_reply (in /lib/x86_64-linux-gnu/libdbus-1.so.3.8.7) ==5716== by 0x403DC4: send_method_call (in /usr/local/bin/connmanctl) ==5716== by 0x4044BD: __connmanctl_dbus_method_call (in /usr/local/bin/connmanctl) ==5716== by 0x409AFF: __connmanctl_monitor_completions (in /usr/local/bin/connmanctl) ==5716== by 0x40A0B6: __connmanctl_input_init (in /usr/local/bin/connmanctl) ==5716== by 0x55F5EC4: (below main) (libc-start.c:287) ==5716== ==5716== LEAK SUMMARY: ==5716== definitely lost: 91 bytes in 3 blocks ==5716== indirectly lost: 72 bytes in 2 blocks ==5716== possibly lost: 0 bytes in 0 blocks ==5716== still reachable: 129,058 bytes in 325 blocks ==5716== suppressed: 0 bytes in 0 blocks ==5716== Reachable blocks (those to which a pointer was found) are not shown. ==5716== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==5716== ==5716== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) ==5716== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) //----------------------------Output End-------------------------------------// However, there were no leaks observed in Connmand Daemon. Abhijit _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
