After compiling a fresh version of valgrind 3.11.0 and running memcheck against an application, I noticed the "Process terminating with default action of signal 4 (SIGILL): dumping core" error.


Also, related or not, one thing to keep in mind is my configuration.
"./configure --target=arm-none-linux-gnueabi --host=arm-linux-gnueabi --prefix=/usr/sbin/valgrind CFLAGS=-static". 
That is the only configuration that seems to work.
However, --host should be set to something different because the machine used for cross-compiling is not an arm-processor. The problem is, if i change my configuration to 
"./configure --target=arm-none-linux-gnueabi --prefix=/usr/sbin CFLAGS=-static --host=x86_64-unknown-linux-gnu", it does not compile.
So, the questin is what should --host be set to?

Upon response, I will attach the entire debug output

Reproducible: Always

Steps to Reproduce:
1.configure valgrind 3.11.0 
2. compile
3. run valgrind against the app

Actual Results:  
==1286== Memcheck, a memory error detector
==1286== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1286== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1286== Command: ./ltel1
==1286== 
--1286-- Valgrind options:
--1286--    -v
--1286-- Contents of /proc/version:
--1286--   Linux version 3.0.51-rt75 (litepoint@rcazeao-o9020ub) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-5
0) ) #2 SMP PREEMPT RT Wed May 25 14:41:22 PDT 2016
--1286-- 
--1286-- Arch and hwcaps: ARM, LittleEndian, ARMv7
--1286-- Page sizes: currently 4096, max supported 4096
--1286-- Valgrind library directory: /usr/sbin/valgrind/lib/valgrind
--1286-- Reading syms from /armlp/lte/fdd/phy/ltel1
--1286-- warning: DiCfSI 0x0 .. 0x3 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x13 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x13 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x2f outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1286-- Reading syms from /lib/ld-2.11.1.so
--1286-- Reading syms from /usr/sbin/valgrind/lib/valgrind/memcheck-arm-linux
--1286--    object doesn't have a dynamic symbol table
--1286-- Scheduler: using generic scheduler lock implementation.
--1286-- Reading suppressions file: /usr/sbin/valgrind/lib/valgrind/default.supp
==1286== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-1286-by-root-on-???
==1286== embedded gdbserver: writing to   /tmp/vgdb-pipe-to-vgdb-from-1286-by-root-on-???
==1286== embedded gdbserver: shared mem   /tmp/vgdb-pipe-shared-mem-vgdb-1286-by-root-on-???
==1286== 
==1286== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1286== don't want to do, unless you know exactly what you're doing,
==1286== or are doing some strange experiment):
==1286==   /usr/sbin/valgrind/lib/valgrind/../../bin/vgdb --pid=1286 ...command...
==1286== 
==1286== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1286==   /path/to/gdb ./ltel1
==1286== and then give GDB the following command
==1286==   target remote | /usr/sbin/valgrind/lib/valgrind/../../bin/vgdb --pid=1286
==1286== --pid is optional if only one valgrind process is running
==1286== 
==1286== 
==1286== Process terminating with default action of signal 4 (SIGILL): dumping core
==1286==  Illegal opcode at address 0x38086EB4
==1286==    at 0x40007A0: ??? (in /lib/ld-2.11.1.so)
==1286== 
==1286== HEAP SUMMARY:
==1286==     in use at exit: 0 bytes in 0 blocks
==1286==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1286== 
==1286== All heap blocks were freed -- no leaks are possible
==1286== 
==1286== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==1286== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction

Expected Results:  
No errors dealing with 
"Process terminating with default action of signal 4 (SIGILL): dumping core"