valgrind SIGILL

\u@\h:\w\$ valgrind /usr/preen/bin/umi_test
==1650== Memcheck, a memory error detector
==1650== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==1650== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==1650== Command: /usr/preen/bin/umi_test
==1650==
disInstr(thumb): unhandled instruction: 0xF3BF 0x8F2F
disInstr(thumb): unhandled instruction: 0xF3BF 0x8F2F
==1650== valgrind: Unrecognised instruction at address 0x4ab80e5.
==1650== Your program just tried to execute an instruction that Valgrind
==1650== did not recognise.  There are two possible reasons for this.
==1650== 1. Your program has a bug and erroneously jumped to a non-code
==1650==    location.  If you are running Memcheck and you just saw a
==1650==    warning about a bad jump, it's probably your program's fault.
==1650== 2. The instruction is legitimate but Valgrind doesn't handle it,
==1650==    i.e. it's Valgrind's fault.  If you think this is the case or
==1650==    you are not sure, please let us know and we'll try to fix it.
==1650== Either way, Valgrind will now raise a SIGILL signal which will
==1650== probably kill your program.
==1650==
==1650== Process terminating with default action of signal 4 (SIGILL)
==1650==  Illegal opcode at address 0x4AB80E5
==1650==    at 0x4AB80E4: __register_atfork (in /lib/libc-2.13.so)
disInstr(thumb): unhandled instruction: 0xF3BF 0x8F2F
==1650== valgrind: Unrecognised instruction at address 0x4ad2343.
==1650== Your program just tried to execute an instruction that Valgrind
==1650== did not recognise.  There are two possible reasons for this.
==1650== 1. Your program has a bug and erroneously jumped to a non-code
==1650==    location.  If you are running Memcheck and you just saw a
==1650==    warning about a bad jump, it's probably your program's fault.
==1650== 2. The instruction is legitimate but Valgrind doesn't handle it,
==1650==    i.e. it's Valgrind's fault.  If you think this is the case or
==1650==    you are not sure, please let us know and we'll try to fix it.
==1650== Either way, Valgrind will now raise a SIGILL signal which will
==1650== probably kill your program.
==1650==
==1650== Process terminating with default action of signal 4 (SIGILL)
==1650==  Illegal opcode at address 0x4AD2343
==1650==    at 0x4AD2342: __libc_freeres (in /lib/libc-2.13.so)
==1650==
==1650== HEAP SUMMARY:
==1650==     in use at exit: 0 bytes in 0 blocks
==1650==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1650==
==1650== All heap blocks were freed -- no leaks are possible
==1650==
==1650== For counts of detected and suppressed errors, rerun with: -v
==1650== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 49 from 5)
Illegal instruction