[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 304321] valgrind: m_signals.c:2314 (sync_signalhandler_from_kernel): Assertion 'tid != 0' faile
From:       Tom Hughes <tom () compton ! nu>
Date:       2012-08-01 11:46:20
Message-ID: bug-304321-17878-wUPQEzuok7 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=304321

--- Comment #9 from Tom Hughes <tom@compton.nu> ---
Hmm... Not sure that helps much. That trace doesn't appear to match the
previous log as it doesn't seem to get as far as reporting the assertion.

What we can see is that valgrind gets as far as exiting, and it is the
exit_group system call which appears to trigger the initial segmentation fault.
That is then followed by each subsequent system call triggering a new
segmentation fault, which makes it impossible for the signal handler to do
anything sensible.

The bad news basically is that your kernel appears to be sending arbitrary segv
signals whenever we try and make a system call, but I can't see any reason for
that so I suspect it is a kernel bug.

The good news is that valgrind had basically finished anyway, so you're not
really missing anything - it has done it's job and it just isn't exiting
cleanly.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]