Hello,
I've tested the new driver for CH347 JTAG chips with valgrind and get
this log:
==439463== 320 bytes in 1 blocks are possibly lost in loss record 11 of 14
==439463== at 0x4848A13: calloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==439463== by 0x4012CE9: calloc (rtld-malloc.h:44)
==439463== by 0x4012CE9: allocate_dtv (dl-tls.c:375)
==439463== by 0x4012CE9: _dl_allocate_tls (dl-tls.c:634)
==439463== by 0x4C8F259: allocate_stack (allocatestack.c:423)
==439463== by 0x4C8F259: pthread_create@@GLIBC_2.34
(pthread_create.c:652)
==439463== by 0x4AE3BCA: ??? (in
/usr/lib/x86_64-linux-gnu/libusb-1.0.so.0.3.0)
==439463== by 0x4AE4A04: libusb_init (in
/usr/lib/x86_64-linux-gnu/libusb-1.0.so.0.3.0)
==439463== by 0x1985D9: jtag_libusb_open (libusb_helper.c:159)
==439463== by 0x1819BD: ch347_open_device (ch347.c:205)
==439463== by 0x184302: ch347_init (ch347.c:1221)
==439463== by 0x171122: adapter_init (adapter.c:148)
==439463== by 0x16E035: handle_init_command (openocd.c:127)
==439463== by 0x2314F9: run_command (command.c:532)
==439463== by 0x232561: exec_command (command.c:908)
Does this means, that the libusb_init call leaks possible memory and I
shouldn't worry about it?
Regards,
Matthias
