https://bugs.kde.org/show_bug.cgi?id=505302
--- Comment #2 from Florian Krohm <[email protected]> --- (In reply to Mark Wielaard from comment #1) > > This might be s390x specific. Not sure - see below. However there are some fixs390 comments in the neighbourhood.... > On x86_64 the native and valgrind behavior are identical. That is not what I see. Run natively, the "with sigsetmp" version runs as expected, the "without sigsetmp" version runs in an infinite loop. Under valgrind (current git) both call the handler once and exit (none and memcheck). This is with a 5.15.0-141 kernel and glibc 2.35 and gcc 11.4.0 on Intel i7-8550U. Unfortunately, I don't know how signal delivery works in general and for s390 in particular.. When we did the s390 port the kernel related stuff was done by Christian Bornträger.. -- You are receiving this mail because: You are watching all bug changes.
