Comment 11 for bug 148465

I think I have the same problem?

valgrind -v ./tst_GMAA_FSPC.debug
==1977== Memcheck, a memory error detector.
==1977== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==1977== Using LibVEX rev 1732, a library for dynamic binary translation.
==1977== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==1977== Using valgrind-3.2.3-Debian, a dynamic binary instrumentation framework.
==1977== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
--1977-- Command line
--1977-- ./tst_GMAA_FSPC.debug
--1977-- Startup, with flags:
--1977-- --suppressions=/usr/lib/valgrind/debian-libc6-dbg.supp
--1977-- -v
--1977-- Contents of /proc/version:
--1977-- Linux version 2.6.18-4-amd64 (Debian 2.6.18.dfsg.1-12etch2) (<email address hidden>) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri May 4 00:37:33 UTC 2007
--1977-- Arch and hwcaps: AMD64, amd64-sse2
--1977-- Page sizes: currently 4096, max supported 4096
--1977-- Valgrind library directory: /usr/lib/valgrind
--1977-- Reading syms from /home/faolieho/Documents/implementation/madp/trunk/src/tests/tst_GMAA_FSPC.debug (0x400000)
--1977-- Reading syms from /lib/ (0x4000000)
--1977-- Reading debug info from /lib/
--1977-- ... CRC mismatch (computed 635CD41D wanted 1F3B7BF3)
--1977-- object doesn't have a symbol table
--1977-- Reading syms from /usr/lib/valgrind/amd64-linux/memcheck (0x38000000)
--1977-- object doesn't have a dynamic symbol table
--1977-- Reading suppressions file: /usr/lib/valgrind/debian-libc6-dbg.supp
--1977-- Reading suppressions file: /usr/lib/valgrind/default.supp
vex amd64->IR: unhandled instruction bytes: 0x66 0x66 0x66 0x66
==1977== valgrind: Unrecognised instruction at address 0x4016321.
==1977== Your program just tried to execute an instruction that Valgrind
==1977== did not recognise. There are two possible reasons for this.
==1977== 1. Your program has a bug and erroneously jumped to a non-code
==1977== location. If you are running Memcheck and you just saw a
==1977== warning about a bad jump, it's probably your program's fault.
==1977== 2. The instruction is legitimate but Valgrind doesn't handle it,
==1977== i.e. it's Valgrind's fault. If you think this is the case or
==1977== you are not sure, please let us know and we'll try to fix it.
==1977== Either way, Valgrind will now raise a SIGILL signal which will
==1977== probably kill your program.
==1977== Process terminating with default action of signal 4 (SIGILL)
==1977== Illegal opcode at address 0x4016321
==1977== at 0x4016321: (within /lib/
==1977== by 0x4007CC2: (within /lib/
==1977== by 0x4003329: (within /lib/
==1977== by 0x4014457: (within /lib/
==1977== by 0x400230A: (within /lib/
==1977== by 0x4000A67: (within /lib/