valgrind --leak-check=yes tvheadend
==7432== Memcheck, a memory error detector
==7432== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==7432== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==7432== Command: tvheadend
==7432==
disInstr(arm): unhandled instruction: 0xF26EE1FE
                 cond=15(0xF) 27:20=38(0x26) 4:4=1 3:0=14(0xE)
==7432== valgrind: Unrecognised instruction at address 0x48f5600.
==7432==    at 0x48F5600: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0)
==7432== Your program just tried to execute an instruction that Valgrind
==7432== did not recognise.  There are two possible reasons for this.
==7432== 1. Your program has a bug and erroneously jumped to a non-code
==7432==    location.  If you are running Memcheck and you just saw a
==7432==    warning about a bad jump, it's probably your program's fault.
==7432== 2. The instruction is legitimate but Valgrind doesn't handle it,
==7432==    i.e. it's Valgrind's fault.  If you think this is the case or
==7432==    you are not sure, please let us know and we'll try to fix it.
==7432== Either way, Valgrind will now raise a SIGILL signal which will
==7432== probably kill your program.
disInstr(arm): unhandled instruction: 0xEE190F1D
                 cond=14(0xE) 27:20=225(0xE1) 4:4=1 3:0=13(0xD)
==7432== valgrind: Unrecognised instruction at address 0x48f5608.
==7432==    at 0x48F5608: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0)
==7432== Your program just tried to execute an instruction that Valgrind
==7432== did not recognise.  There are two possible reasons for this.
==7432== 1. Your program has a bug and erroneously jumped to a non-code
==7432==    location.  If you are running Memcheck and you just saw a
==7432==    warning about a bad jump, it's probably your program's fault.
==7432== 2. The instruction is legitimate but Valgrind doesn't handle it,
==7432==    i.e. it's Valgrind's fault.  If you think this is the case or
==7432==    you are not sure, please let us know and we'll try to fix it.
==7432== Either way, Valgrind will now raise a SIGILL signal which will
==7432== probably kill your program.
disInstr(arm): unhandled instruction: 0xF1010200
                 cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0)
==7432== valgrind: Unrecognised instruction at address 0x4843588.
==7432==    at 0x4843588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==7432== Your program just tried to execute an instruction that Valgrind
==7432== did not recognise.  There are two possible reasons for this.
==7432== 1. Your program has a bug and erroneously jumped to a non-code
==7432==    location.  If you are running Memcheck and you just saw a
==7432==    warning about a bad jump, it's probably your program's fault.
==7432== 2. The instruction is legitimate but Valgrind doesn't handle it,
==7432==    i.e. it's Valgrind's fault.  If you think this is the case or
==7432==    you are not sure, please let us know and we'll try to fix it.
==7432== Either way, Valgrind will now raise a SIGILL signal which will
==7432== probably kill your program.
==7432==
==7432== Process terminating with default action of signal 4 (SIGILL)
==7432==  Illegal opcode at address 0x4843588
==7432==    at 0x4843588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==7432==
==7432== HEAP SUMMARY:
==7432==     in use at exit: 62,975 bytes in 159 blocks
==7432==   total heap usage: 201 allocs, 42 frees, 67,123 bytes allocated
==7432==
==7432== 17 bytes in 1 blocks are possibly lost in loss record 1 of 12
==7432==    at 0x48353C4: operator new(unsigned int) (vg_replace_malloc.c:282)
==7432==    by 0x6224F9B: std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator<char> const&) (in /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.17)
==7432==
==7432== 152 bytes in 1 blocks are possibly lost in loss record 9 of 12
==7432==    at 0x4833C54: calloc (vg_replace_malloc.c:566)
==7432==    by 0x40117F3: allocate_dtv (dl-tls.c:300)
==7432==    by 0x4011ED3: _dl_allocate_tls (dl-tls.c:464)
==7432==    by 0x57377B7: pthread_create@@GLIBC_2.4 (allocatestack.c:580)
==7432==    by 0x113D7: tvhlog_start (tvhlog.c:425)
==7432==    by 0xFA67: main (main.c:755)
==7432==
==7432== LEAK SUMMARY:
==7432==    definitely lost: 0 bytes in 0 blocks
==7432==    indirectly lost: 0 bytes in 0 blocks
==7432==      possibly lost: 169 bytes in 2 blocks
==7432==    still reachable: 62,806 bytes in 157 blocks
==7432==         suppressed: 0 bytes in 0 blocks
==7432== Reachable blocks (those to which a pointer was found) are not shown.
==7432== To see them, rerun with: --leak-check=full --show-reachable=yes
==7432==
==7432== For counts of detected and suppressed errors, rerun with: -v
==7432== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 93 from 6)
Killed
hts@(none):/home/pi$