https://bugs.kde.org/show_bug.cgi?id=452274
--- Comment #21 from Nick Briggs <afraid-splicer...@icloud.com> --- Here's what happens with --trace-signals=yes and using the write(...) as the thing to be interrupted: DEBUG: vgPlain_client_syscall sysno 4 DEBUG: vgPlain_client_syscall sysno 4 DEBUG: vgPlain_client_syscall sysno 4 DEBUG: vgPlain_client_syscall sysno 4 DEBUG: vgPlain_client_syscall sysno 4 DEBUG: vgPlain_client_syscall sysno 4 --12231-- async signal handler: signal=26, vgtid=100118, tid=1, si_code=65542, exitreason VgSrc_None --12231-- interrupted_syscall: tid=1, ip=0x381a1e02, restart=False, sres.isErr=False, sres.val=0 --12231-- not started: restarting --12231-- delivering signal 26 (SIGVTALRM):65542 to thread 1 --12231-- push_signal_frame (thread 1): signal 26 ==12231== at 0x7303DBD: _write (in /lib/libc.so.7) ==12231== by 0x730236E: write (in /lib/libc.so.7) ==12231== by 0x4018ED: main (in /var/tmp/vgtest2) DEBUG: vgPlain_client_syscall sysno 1000 --12231-- VG_(signal_return) (thread 1): EIP=0x7303dbd DEBUG: vgPlain_client_syscall sysno 4 DEBUG: vgPlain_client_syscall sysno 4 DEBUG: vgPlain_client_syscall sysno 4 --12231-- async signal handler: signal=26, vgtid=100118, tid=1, si_code=65542, exitreason VgSrc_None --12231-- interrupted_syscall: tid=1, ip=0x381e4921, restart=False, sres.isErr=False, sres.val=0 --12231-- not in syscall at all: hmm, very suspicious --12231-- delivering signal 26 (SIGVTALRM):65542 to thread 1 --12231-- push_signal_frame (thread 1): signal 26 ==12231== at 0x7303DBF: _write (in /lib/libc.so.7) ==12231== by 0x730236E: write (in /lib/libc.so.7) ==12231== by 0x4018ED: main (in /var/tmp/vgtest2) DEBUG: vgPlain_client_syscall sci->status.what 2 DEBUG: vgPlain_client_syscall sysno 1000 valgrind: m_syswrap/syswrap-main.c:2142 (void vgPlain_client_syscall(ThreadId, UInt)): Assertion 'sci->status.what == SsIdle' failed. host stacktrace: ==12231== at 0x38116B19: ??? (in /usr/home/briggs/valgrind/memcheck/memcheck-x86-freebsd) ==12231== by 0x38116DF6: ??? (in /usr/home/briggs/valgrind/memcheck/memcheck-x86-freebsd) sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 1000 (lwpid 100118) ==12231== at 0x381A0821: ??? (in /usr/home/briggs/valgrind/memcheck/memcheck-x86-freebsd) ==12231== by 0x4018ED: main (in /var/tmp/vgtest2) client stack range: [0xFBBFC000 0xFBBFEFFF] client SP: 0xFBBFE1E8 valgrind stack range: [0x51BE000 0x52BDFFF] top usage: 5792 of 1048576 Where the "very suspicious" message is from coregrind/m_syswrap/syswrap-main.c -- You are receiving this mail because: You are watching all bug changes.
