[Valgrind-users] Valgrind fails to perform

[Igor K. <iko...@gm...>]

Hi, ALL,

My name is Igor and I'm a cross-platform developer.

Recently my program started experiencing crashes, so I decided to try valgrind.

Here is the session:

[code]
igor@WaylandGnome ~/dbhandler/Debug/dbhandler $ valgrind
--leak-check=yes ./dbhandler
==16807== Memcheck, a memory error detector
==16807== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==16807== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==16807== Command: ./dbhandler
==16807==
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD0
0x8 0x4 0x0 0x0 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=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==16807== valgrind: Unrecognised instruction at address 0x40149d7.
==16807==    at 0x40149D7: get_common_indices.constprop.0 (in
/lib64/ld-linux-x86-64.so.2)
==16807==    by 0x401604E: init_cpu_features.constprop.0 (in
/lib64/ld-linux-x86-64.so.2)
==16807==    by 0x4016360: _dl_x86_init_cpu_features (in
/lib64/ld-linux-x86-64.so.2)
==16807==    by 0x401974B: _dl_sysdep_start (in /lib64/ld-linux-x86-64.so.2)
==16807==    by 0x401AECD: _dl_start (in /lib64/ld-linux-x86-64.so.2)
==16807==    by 0x4019D17: ??? (in /lib64/ld-linux-x86-64.so.2)
==16807== Your program just tried to execute an instruction that Valgrind
==16807== did not recognise.  There are two possible reasons for this.
==16807== 1. Your program has a bug and erroneously jumped to a non-code
==16807==    location.  If you are running Memcheck and you just saw a
==16807==    warning about a bad jump, it's probably your program's fault.
==16807== 2. The instruction is legitimate but Valgrind doesn't handle it,
==16807==    i.e. it's Valgrind's fault.  If you think this is the case or
==16807==    you are not sure, please let us know and we'll try to fix it.
==16807== Either way, Valgrind will now raise a SIGILL signal which will
==16807== probably kill your program.
==16807==
==16807== Process terminating with default action of signal 4 (SIGILL)
==16807==  Illegal opcode at address 0x40149D7
==16807==    at 0x40149D7: get_common_indices.constprop.0 (in
/lib64/ld-linux-x86-64.so.2)
==16807==    by 0x401604E: init_cpu_features.constprop.0 (in
/lib64/ld-linux-x86-64.so.2)
==16807==    by 0x4016360: _dl_x86_init_cpu_features (in
/lib64/ld-linux-x86-64.so.2)
==16807==    by 0x401974B: _dl_sysdep_start (in /lib64/ld-linux-x86-64.so.2)
==16807==    by 0x401AECD: _dl_start (in /lib64/ld-linux-x86-64.so.2)
==16807==    by 0x4019D17: ??? (in /lib64/ld-linux-x86-64.so.2)
==16807==
==16807== HEAP SUMMARY:
==16807==     in use at exit: 0 bytes in 0 blocks
==16807==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==16807==
==16807== All heap blocks were freed -- no leaks are possible
==16807==
==16807== For lists of detected and suppressed errors, rerun with: -s
==16807== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction
[/code]

What is the problem?

I'm running Gentoo Linux.

Thank you.