Bug 299803 - vex amd64->IR: unhandled instruction bytes: 0xC5 0xF1 0x57 0xC9 0xC5 0xF9 0x2E 0xC8
Summary: vex amd64->IR: unhandled instruction bytes: 0xC5 0xF1 0x57 0xC9 0xC5 0xF9 0x2...
Status: RESOLVED DUPLICATE of bug 273475
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
Depends on:
Reported: 2012-05-11 09:25 UTC by David Sveningsson
Modified: 2012-05-11 09:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description David Sveningsson 2012-05-11 09:25:38 UTC
--3918-- REDIR: 0x3fed684ab0 (strcspn) redirected to 0x4802667 (_vgnU_ifunc_wrapper)
==3918== Adding active redirection:
--3918--     new: 0x3fed7269d0 (__strcspn_sse42     ) R-> (2033.0) 0x04a0ade1 strcspn
--3918-- REDIR: 0x3fed7269d0 (__strcspn_sse42) redirected to 0x4a0ade1 (strcspn)
vex amd64->IR: unhandled instruction bytes: 0xC5 0xF1 0x57 0xC9 0xC5 0xF9 0x2E 0xC8
==3918== valgrind: Unrecognised instruction at address 0x3feda22200.
==3918==    at 0x3FEDA22200: log (w_log.c:29)
==3918==    by 0x6632946: ??? (in /usr/lib64/libnvidia-glcore.so.295.49)
==3918== Your program just tried to execute an instruction that Valgrind
==3918== did not recognise.  There are two possible reasons for this.
==3918== 1. Your program has a bug and erroneously jumped to a non-code
==3918==    location.  If you are running Memcheck and you just saw a
==3918==    warning about a bad jump, it's probably your program's fault.
==3918== 2. The instruction is legitimate but Valgrind doesn't handle it,
==3918==    i.e. it's Valgrind's fault.  If you think this is the case or
==3918==    you are not sure, please let us know and we'll try to fix it.
==3918== Either way, Valgrind will now raise a SIGILL signal which will
==3918== probably kill your program.
==3918== Process terminating with default action of signal 4 (SIGILL)
==3918==  Illegal opcode at address 0x3FEDA22200
==3918==    at 0x3FEDA22200: log (w_log.c:29)
==3918==    by 0x6632946: ??? (in /usr/lib64/libnvidia-glcore.so.295.49)
--3918-- Caught __NR_exit; running __libc_freeres()

Reproducible: Always

# cat /proc/cpuinfo
processor       : 7
vendor_id       : GenuineIntel
cpu family      : 6
model           : 42
model name      : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
stepping        : 7
microcode       : 0x17
cpu MHz         : 3401.000
cache size      : 8192 KB
physical id     : 0
siblings        : 8
core id         : 3
cpu cores       : 4
apicid          : 7
initial apicid  : 7
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid
bogomips        : 6822.91
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

# grep CFLAGS /etc/make.conf
CFLAGS="-march=native -Os -pipe -msse3 -g -ggdb"
# gcc -v 2>&1 | grep "gcc version"
gcc version 4.6.3 (Gentoo 4.6.3 p1.0, pie-0.5.1) 
# uname -a
Linux nanako 3.3.1-gentoo #3 SMP Wed Apr 11 00:24:54 CEST 2012 x86_64 Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz GenuineIntel GNU/Linux
Comment 1 Tom Hughes 2012-05-11 09:37:35 UTC

*** This bug has been marked as a duplicate of bug 273475 ***