https://bugs.kde.org/show_bug.cgi?id=507188
Mark Wielaard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |CONFIRMED CC| |[email protected] Ever confirmed|0 |1 --- Comment #2 from Mark Wielaard <[email protected]> --- Could reproduce on Debian i686 (but not on any other arch). This issue seems to have been triggered by this commit: commit 41441379baa63b5471385361d08c8df317705b69 Author: Mark Wielaard <[email protected]> Date: Sun Mar 30 17:38:21 2025 +0200 Handle top __syscall_cancel frames when getting stack traces Since glibc 2.41 there are extra frames inserted before doing a syscall to support proper thread cancellation. This breaks various suppressions and regtests involving checking syscall arguments. Solve this by removing those extra frames from the top of the call stack when we are processing a linux system call. https://bugs.kde.org/show_bug.cgi?id=502126 This also removed the _dl_sysinfo_int80 call. Looks like for some reason there isn't anything left after that, so n_ips == 0, triggering the assert. -- You are receiving this mail because: You are watching all bug changes.
