https://bugs.kde.org/show_bug.cgi?id=469878
Bug ID: 469878
Summary: unhandled instruction bytes: 0x62 0xF1 0x7F 0x48 0x7F
0x44 0x24 0x1 0x83 0xE7
Classification: Developer tools
Product: valgrind
Version: 3.20.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: tus...@kazv.moe
Target Milestone: ---
Created attachment 159023
--> https://bugs.kde.org/attachment.cgi?id=159023&action=edit
cpuinfo
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. valgrind ls
2.
3.
OBSERVED RESULT
==8232== Memcheck, a memory error detector
==8232== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==8232== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==8232== Command: ls
==8232==
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7F 0x48 0x7F 0x44 0x24
0x1 0x83 0xE7
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
==8232== valgrind: Unrecognised instruction at address 0x401c126.
==8232== at 0x401C126: _dl_start (rtld.c:566)
==8232== by 0x401B1D7: ??? (in /lib64/ld-linux-x86-64.so.2)
==8232== Your program just tried to execute an instruction that Valgrind
==8232== did not recognise. There are two possible reasons for this.
==8232== 1. Your program has a bug and erroneously jumped to a non-code
==8232== location. If you are running Memcheck and you just saw a
==8232== warning about a bad jump, it's probably your program's fault.
==8232== 2. The instruction is legitimate but Valgrind doesn't handle it,
==8232== i.e. it's Valgrind's fault. If you think this is the case or
==8232== you are not sure, please let us know and we'll try to fix it.
==8232== Either way, Valgrind will now raise a SIGILL signal which will
==8232== probably kill your program.
==8232==
==8232== Process terminating with default action of signal 4 (SIGILL): dumping
core
==8232== Illegal opcode at address 0x401C126
==8232== at 0x401C126: _dl_start (rtld.c:566)
==8232== by 0x401B1D7: ??? (in /lib64/ld-linux-x86-64.so.2)
==8232==
==8232== HEAP SUMMARY:
==8232== in use at exit: 0 bytes in 0 blocks
==8232== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==8232==
==8232== All heap blocks were freed -- no leaks are possible
==8232==
==8232== For lists of detected and suppressed errors, rerun with: -s
==8232== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
EXPECTED RESULT
it should work
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 6.1.27
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
/proc/cpuinfo is attached.
This is a Gentoo compiled with
*/* CPU_FLAGS_X86: aes avx avx2 avx512f avx512dq avx512cd avx512bw avx512vl
avx512vbmi f16c fma3 mmx mmxext pclmul popcnt rdrand sha sse sse2 sse3 sse4_1
sse4_2 sse4a ssse3
and glibc is compiled with
CFLAGS="${CFLAGS} -fno-builtin-strlen -ggdb3"
CXXFLAGS="${CXXFLAGS} -ggdb3"
FEATURES="${FEATURES} splitdebug compressdebug -nostrip installsources"
--
You are receiving this mail because:
You are watching all bug changes.
