https://bugs.kde.org/show_bug.cgi?id=522489
--- Comment #29 from echedey-ls <[email protected]> --- Thanks for sharing the complete valgrind call, I was trying something close (--track-origins=yes and --trace-children=yes). This is what I get with that command: ❯ valgrind --track-origins=yes --num-callers=25 --leak-check=full kded6 --replace ==5418== Memcheck, a memory error detector ==5418== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==5418== Using Valgrind-3.25.1 and LibVEX; rerun with -h for copyright info ==5418== Command: kded6 --replace ==5418== vex amd64->IR: unhandled instruction bytes: 0x62 0xF3 0xF5 0x28 0x38 0xC8 0x1 0xC4 0xE3 0xC1 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 ==5418== valgrind: Unrecognised instruction at address 0x84d3709. ==5418== at 0x84D3709: UnknownInlinedFun (glvnd_pthread.c:463) ==5418== by 0x84D3709: __glDispatchOnLoadInit (GLdispatch.c:174) ==5418== by 0x401F1EE: call_init (dl-init.c:74) ==5418== by 0x401F1EE: call_init (dl-init.c:26) ==5418== by 0x401F2CC: _dl_init (dl-init.c:121) ==5418== by 0x403A8BF: ??? (in /usr/lib/ld-linux-x86-64.so.2) ==5418== by 0x1: ??? ==5418== by 0x1FFF000016: ??? ==5418== by 0x1FFF00001C: ??? ==5418== Your program just tried to execute an instruction that Valgrind ==5418== did not recognise. There are two possible reasons for this. ==5418== 1. Your program has a bug and erroneously jumped to a non-code ==5418== location. If you are running Memcheck and you just saw a ==5418== warning about a bad jump, it's probably your program's fault. ==5418== 2. The instruction is legitimate but Valgrind doesn't handle it, ==5418== i.e. it's Valgrind's fault. If you think this is the case or ==5418== you are not sure, please let us know and we'll try to fix it. ==5418== Either way, Valgrind will now raise a SIGILL signal which will ==5418== probably kill your program. ==5418== ==5418== Process terminating with default action of signal 4 (SIGILL): dumping core ==5418== Illegal opcode at address 0x84D3709 ==5418== at 0x84D3709: UnknownInlinedFun (glvnd_pthread.c:463) ==5418== by 0x84D3709: __glDispatchOnLoadInit (GLdispatch.c:174) ==5418== by 0x401F1EE: call_init (dl-init.c:74) ==5418== by 0x401F1EE: call_init (dl-init.c:26) ==5418== by 0x401F2CC: _dl_init (dl-init.c:121) ==5418== by 0x403A8BF: ??? (in /usr/lib/ld-linux-x86-64.so.2) ==5418== by 0x1: ??? ==5418== by 0x1FFF000016: ??? ==5418== by 0x1FFF00001C: ??? ==5418== ==5418== HEAP SUMMARY: ==5418== in use at exit: 104 bytes in 2 blocks ==5418== total heap usage: 2 allocs, 0 frees, 104 bytes allocated ==5418== ==5418== LEAK SUMMARY: ==5418== definitely lost: 0 bytes in 0 blocks ==5418== indirectly lost: 0 bytes in 0 blocks ==5418== possibly lost: 0 bytes in 0 blocks ==5418== still reachable: 104 bytes in 2 blocks ==5418== suppressed: 0 bytes in 0 blocks ==5418== Reachable blocks (those to which a pointer was found) are not shown. ==5418== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==5418== ==5418== For lists of detected and suppressed errors, rerun with: -s ==5418== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) fish: Job 1, 'valgrind --track-origins=yes --…' terminated by signal SIGILL (Illegal instruction) I must note that I'm on CachyOS, and many packages are installed from cachyos-v4, cachyos-core-v4 or cachyos-extra-v4, and therefore have different ABIs. I have already had problems related to that (debug symbols being for bare Arch core, but having libs with v4 optimizations). I did check the repos I'm using for what I think is the main software involved, to be those from bare arch: ❯ pacman -Qi glibc glibc-debug valgrind kded | grep "From" Installed From : core Installed From : core-debug Installed From : extra Installed From : extra I don't know what else to do. Once again, thank you for the support. -- You are receiving this mail because: You are watching all bug changes.
