I have never used cachegrind, but I’ve seen a similar message before when using
memcheck.
In my case, the problem was that I was using the wrong version of memcheck for
my CPU type.
For example, I think I was trying to run a 32-bit version of memcheck with a
64-bit executable.
Ben
From:
vex amd64->IR: unhandled instruction bytes: 0xF3 0xF 0x1E 0xFA 0x41 0x56 0x41
0x89
Follow the Bug Reports link at http://valgrind.org to file a bug report
at http://bugs.kde.org/query.cgi?format=specific .
Please be sure to state the version of valgrind. Run "valgrind --version".
The
Hello guys,
I'm currently trying to profile my program's cache behaviour using
cachegrind. I can confirm the program seems to be working as I first tested
cachegrind compiling my code with GCC. The problem is that I'm now using
Intel C compiler and for some reason I keep getting the same error as
