valgrid output pilight

disInstr(arm): unhandled instruction: 0xF26EE1FE
                 cond=15(0xF) 27:20=38(0x26) 4:4=1 3:0=14(0xE)
==2976== valgrind: Unrecognised instruction at address 0x49435e0.
==2976==    at 0x49435E0: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0)
==2976== Your program just tried to execute an instruction that Valgrind
==2976== did not recognise.  There are two possible reasons for this.
==2976== 1. Your program has a bug and erroneously jumped to a non-code
==2976==    location.  If you are running Memcheck and you just saw a
==2976==    warning about a bad jump, it's probably your program's fault.
==2976== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2976==    i.e. it's Valgrind's fault.  If you think this is the case or
==2976==    you are not sure, please let us know and we'll try to fix it.
==2976== Either way, Valgrind will now raise a SIGILL signal which will
==2976== probably kill your program.
disInstr(arm): unhandled instruction: 0xEE190F1D
                 cond=14(0xE) 27:20=225(0xE1) 4:4=1 3:0=13(0xD)
==2976== valgrind: Unrecognised instruction at address 0x49435e8.
==2976==    at 0x49435E8: ??? (in /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0)
==2976== Your program just tried to execute an instruction that Valgrind
==2976== did not recognise.  There are two possible reasons for this.
==2976== 1. Your program has a bug and erroneously jumped to a non-code
==2976==    location.  If you are running Memcheck and you just saw a
==2976==    warning about a bad jump, it's probably your program's fault.
==2976== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2976==    i.e. it's Valgrind's fault.  If you think this is the case or
==2976==    you are not sure, please let us know and we'll try to fix it.
==2976== Either way, Valgrind will now raise a SIGILL signal which will
==2976== probably kill your program.
==2951== Thread 7:
==2951== Invalid read of size 4
==2951==    at 0x4974144: fclose@@GLIBC_2.4 (iofclose.c:57)
==2951==    by 0xAA9F: call_process_file (daemon.c:172)
==2951==    by 0x48FDBFB: start_thread (pthread_create.c:306)
==2951==    by 0x49E0757: ??? (clone.S:116)
==2951==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==2951==
pi@raspberrypi ~/pilight.dev $ disInstr(arm): unhandled instruction: 0xF1010200
                 cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0)
==2976== valgrind: Unrecognised instruction at address 0x4843638.
==2976==    at 0x4843638: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==2976== Your program just tried to execute an instruction that Valgrind
==2976== did not recognise.  There are two possible reasons for this.
==2976== 1. Your program has a bug and erroneously jumped to a non-code
==2976==    location.  If you are running Memcheck and you just saw a
==2976==    warning about a bad jump, it's probably your program's fault.
==2976== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2976==    i.e. it's Valgrind's fault.  If you think this is the case or
==2976==    you are not sure, please let us know and we'll try to fix it.
==2976== Either way, Valgrind will now raise a SIGILL signal which will
==2976== probably kill your program.
==2976==
==2976== Process terminating with default action of signal 4 (SIGILL)
==2976==  Illegal opcode at address 0x4843638
==2976==    at 0x4843638: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==2976==
==2976== HEAP SUMMARY:
==2976==     in use at exit: 1,327,221 bytes in 272 blocks
==2976==   total heap usage: 303 allocs, 31 frees, 1,331,069 bytes allocated
==2976==
==2976== LEAK SUMMARY:
==2976==    definitely lost: 0 bytes in 0 blocks
==2976==    indirectly lost: 0 bytes in 0 blocks
==2976==      possibly lost: 0 bytes in 0 blocks
==2976==    still reachable: 1,327,221 bytes in 272 blocks
==2976==         suppressed: 0 bytes in 0 blocks
==2976== Reachable blocks (those to which a pointer was found) are not shown.
==2976== To see them, rerun with: --leak-check=full --show-reachable=yes
==2976==
==2976== For counts of detected and suppressed errors, rerun with: -v
==2976== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 67 from 8)
Illegal instruction
==2971==
==2971== HEAP SUMMARY:
==2971==     in use at exit: 478 bytes in 23 blocks
==2971==   total heap usage: 25 allocs, 2 frees, 538 bytes allocated
==2971==
==2971== LEAK SUMMARY:
==2971==    definitely lost: 0 bytes in 0 blocks
==2971==    indirectly lost: 0 bytes in 0 blocks
==2971==      possibly lost: 0 bytes in 0 blocks
==2971==    still reachable: 478 bytes in 23 blocks
==2971==         suppressed: 0 bytes in 0 blocks
==2971== Reachable blocks (those to which a pointer was found) are not shown.
==2971== To see them, rerun with: --leak-check=full --show-reachable=yes
==2971==
==2971== For counts of detected and suppressed errors, rerun with: -v
==2971== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 6)
==2991== Memcheck, a memory error detector
==2991== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==2991== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==2991== Command: /home/pi/scripts/pilight-event.php {"origin":"sender","protocol":"archtech_switches","code":{"id":8934706,"unit":3,"state":"off"}}
==2991==