Bug 303466

Summary:	vex amd64->IR: unhandled instruction bytes: 0xC5 0x7A 0x10 0x35 0x61 0x2D 0x20 0x0
Product:	[Developer tools] valgrind	Reporter:	Paul Melis <paul.melis>
Component:	vex	Assignee:	Julian Seward <jseward>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	3.7.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Paul Melis 2012-07-13 12:16:09 UTC

I see no memcheck errors in the valgrind output, and also running my program under libefence shows no problems. So I assume that this really is a valgrind bug. Happens both with memcheck and helgrind.

Program this happens with is some custom code that I can't easily share, nor does it do anything very exotic (communication over sockets and some multithreaded computations). GCC version, in case it matters, is 4.4.3. Linux x86_64, kernel 2.6.23-41, Ubuntu 10.04.4 LTS. Valgrind is version compiled by myself, not the Ubuntu-included 3.6.0 (which has the same problem).

Reproducible: Always

Comment 1 Julian Seward 2012-07-13 12:21:05 UTC

It's an AVX instruction.  AVX is supported in the trunk now.  
  svn co svn://svn.valgrind.org/valgrind/trunk
  cd trunk
  ./autogen.sh
Then configure and build as normal.

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