valgrind wash -i wlan1mon

valgrind wash -i wlan1mon
==23248== Memcheck, a memory error detector
==23248== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==23248== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==23248== Command: wash -i wlan1mon
==23248==
==23248== Conditional jump or move depends on uninitialised value(s)
==23248==    at 0x407364C: ??? (in /lib/libc.so)
==23248==    by 0x408492C: ??? (in /lib/libc.so)
==23248==
==23248== Conditional jump or move depends on uninitialised value(s)
==23248==    at 0x4072AD8: ??? (in /lib/libc.so)
==23248==    by 0x40730A0: ??? (in /lib/libc.so)
==23248==
==23248== Conditional jump or move depends on uninitialised value(s)
==23248==    at 0x407366C: ??? (in /lib/libc.so)
==23248==    by 0x408492C: ??? (in /lib/libc.so)
==23248==
vex mips->IR: unhandled instruction bytes: 0x4 0x64 0xF5 0x9D
==23248== valgrind: Unrecognised instruction at address 0x401b71.
==23248==    at 0x401B71: ??? (in /usr/bin/wash)
==23248==    by 0x401CE20: ??? (in /lib/libc.so)
==23248== Your program just tried to execute an instruction that Valgrind
==23248== did not recognise.  There are two possible reasons for this.
==23248== 1. Your program has a bug and erroneously jumped to a non-code
==23248==    location.  If you are running Memcheck and you just saw a
==23248==    warning about a bad jump, it's probably your program's fault.
==23248== 2. The instruction is legitimate but Valgrind doesn't handle it,
==23248==    i.e. it's Valgrind's fault.  If you think this is the case or
==23248==    you are not sure, please let us know and we'll try to fix it.
==23248== Either way, Valgrind will now raise a SIGILL signal which will
==23248== probably kill your program.
==23248==
==23248== Process terminating with default action of signal 4 (SIGILL)
==23248==  Illegal opcode at address 0x401B71
==23248==    at 0x401B71: ??? (in /usr/bin/wash)
==23248==    by 0x401CE20: ??? (in /lib/libc.so)
==23248==
==23248== HEAP SUMMARY:
==23248==     in use at exit: 0 bytes in 0 blocks
==23248==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==23248==
==23248== All heap blocks were freed -- no leaks are possible
==23248==
==23248== Use --track-origins=yes to see where uninitialised values come from
==23248== For lists of detected and suppressed errors, rerun with: -s
==23248== ERROR SUMMARY: 4 errors from 3 contexts (suppressed: 0 from 0)
Illegal instruction