Re: valgrind: Unrecognised instruction

Ben White <[email protected]>
Newsgroups gmane.comp.debugging.valgrind
Message-ID <BY5PR16MB32404195B06B14EF163CD15984020@BY5PR16MB3240.namprd16.prod.outlook.com>
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: Alexandre Azevedo <[email protected]>
Sent: Wednesday, February 5, 2020 10:50 AM
To: [email protected]
Subject: [Valgrind-users] valgrind: Unrecognised instruction

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 I try to run it with cachegrind. Following is the error message.


vex amd64->IR: unhandled instruction bytes: 0xF3 0xF 0x1E 0xFA 0x41 0x56 0x41 0x89
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=1
==23029== valgrind: Unrecognised instruction at address 0x4032e0.
==23029==    at 0x4032E0: __intel_new_feature_proc_init (in /home/arthur/Documentos/Prog.Paralela/intelseqkron)
==23029==    by 0x565282F: (below main) (libc-start.c:291)
==23029== Your program just tried to execute an instruction that Valgrind
==23029== did not recognise.  There are two possible reasons for this.
==23029== 1. Your program has a bug and erroneously jumped to a non-code
==23029==    location.  If you are running Memcheck and you just saw a
==23029==    warning about a bad jump, it's probably your program's fault.
==23029== 2. The instruction is legitimate but Valgrind doesn't handle it,
==23029==    i.e. it's Valgrind's fault.  If you think this is the case or
==23029==    you are not sure, please let us know and we'll try to fix it.
==23029== Either way, Valgrind will now raise a SIGILL signal which will
==23029== probably kill your program.
==23029==
==23029== Process terminating with default action of signal 4 (SIGILL)
==23029==  Illegal opcode at address 0x4032E0
==23029==    at 0x4032E0: __intel_new_feature_proc_init (in /home/arthur/Documentos/Prog.Paralela/intelseqkron)
==23029==    by 0x565282F: (below main) (libc-start.c:291)
==23029==


My best regards,

Alexandre

_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.