https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #20 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- The below trace might show that the special signal (64) used by valgrind to get a thread out of a syscall has been masked. If that is the case, it should be relatively easy to write a reproducer: * launch a thread that masks the signal 64 and then calls sigsuspend * have the main thread calling exit once this thread is in sigsuspend. Note that I have filed bug 372600, which is also a process not dying (but I do not think it is your problem) SYSCALL[10966,1](14) sys_rt_sigprocmask ( 0, 0xffeffeaf0, 0x0, 8 )--10966-- do_setmask: tid = 1 how = 0 (SIG_BLOCK), newset = 0xFFEFFEAF0 (fffffffe7ffffb77) SYSCALL[10966,2](14) sys_rt_sigprocmask ( 2, 0x4039e90, 0x0, 8 )--10966-- do_setmask: tid = 2 how = 2 (SIG_SETMASK), newset = 0x4039E90 (fffffffe7fffbffb) SYSCALL[10966,2](130) sys_rt_sigsuspend ( 0x4039e90, 8 ) --> [async] ... SYSCALL[10966,3](14) sys_rt_sigprocmask ( 2, 0x403de90, 0x0, 8 )--10966-- do_setmask: tid = 3 how = 2 (SIG_SETMASK), newset = 0x403DE90 (fffffffe7ffeffff) SYSCALL[10966,3](130) sys_rt_sigsuspend ( 0x403de90, 8 ) --> [async] ... SYSCALL[10966,1](13) sys_rt_sigaction ( 15, 0xffeffe9a0, 0x0, 8 )--10966-- -- You are receiving this mail because: You are watching all bug changes.
