https://bugs.kde.org/show_bug.cgi?id=492886
--- Comment #3 from localtoast <ipsum.te.fu...@gmail.com> --- (In reply to Sam James from comment #2) > Are you able to reproduce it under Valgrind by the way? I remember asking on > the forums about ASAN + UBSAN but I don't remember if anyone tried it or it > got any results. I have the following valgrind output, which I doubt is useful. Libc is not compiled with debug symbols yet (truthfully I'm not super keen on doing that if not absolutely necessary), and this is my first ever attempt at debugging anything with valgrind. ==9216== Memcheck, a memory error detector ==9216== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==9216== Using Valgrind-3.23.1.GIT and LibVEX; rerun with -h for copyright info ==9216== Command: plasmashell ==9216== 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 ==9216== valgrind: Unrecognised instruction at address 0x4014eaf. ==9216== at 0x4014EAF: get_common_indices.constprop.0 (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x4016C77: init_cpu_features.constprop.0 (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x4017148: _dl_x86_init_cpu_features (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x401ADE7: _dl_sysdep_start (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x401C52B: _dl_start (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x401B417: ??? (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== Your program just tried to execute an instruction that Valgrind ==9216== did not recognise. There are two possible reasons for this. ==9216== 1. Your program has a bug and erroneously jumped to a non-code ==9216== location. If you are running Memcheck and you just saw a ==9216== warning about a bad jump, it's probably your program's fault. ==9216== 2. The instruction is legitimate but Valgrind doesn't handle it, ==9216== i.e. it's Valgrind's fault. If you think this is the case or ==9216== you are not sure, please let us know and we'll try to fix it. ==9216== Either way, Valgrind will now raise a SIGILL signal which will ==9216== probably kill your program. ==9216== ==9216== Process terminating with default action of signal 4 (SIGILL) ==9216== Illegal opcode at address 0x4014EAF ==9216== at 0x4014EAF: get_common_indices.constprop.0 (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x4016C77: init_cpu_features.constprop.0 (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x4017148: _dl_x86_init_cpu_features (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x401ADE7: _dl_sysdep_start (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x401C52B: _dl_start (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== by 0x401B417: ??? (in /usr/lib64/ld-linux-x86-64.so.2) ==9216== ==9216== HEAP SUMMARY: ==9216== in use at exit: 0 bytes in 0 blocks ==9216== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==9216== ==9216== All heap blocks were freed -- no leaks are possible ==9216== ==9216== For lists of detected and suppressed errors, rerun with: -s ==9216== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) -- You are receiving this mail because: You are watching all bug changes.
