https://bugs.kde.org/show_bug.cgi?id=410599
--- Comment #3 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Stefan Maksimovic from comment #2) > If it's not too much trouble, I suggest you test it yourself just to make > sure. I tested, and the modified test still reproduces the bug with the old release (and is working ok with the new release). However, the test itself is now using uninitialised variables: ==32132== Syscall param rt_sigaction(act->sa_mask) points to uninitialised byte(s) ==32132== at 0x487D800: __libc_sigaction (sigaction.c:58) ==32132== by 0x109266: main (pth_self_kill.c:39) ==32132== Address 0x1ffefffd08 is on thread 1's stack ==32132== in frame #0, created by __libc_sigaction (sigaction.c:43) ==32132== ==32132== Syscall param rt_sigaction(act->sa_flags) points to uninitialised byte(s) ==32132== at 0x487D800: __libc_sigaction (sigaction.c:58) ==32132== by 0x109266: main (pth_self_kill.c:39) ==32132== Address 0x1ffefffcf8 is on thread 1's stack ==32132== in frame #0, created by __libc_sigaction (sigaction.c:43) That should better be fixed to ensure we have a deterministic test :). -- You are receiving this mail because: You are watching all bug changes.