<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [sna] Random X-Server crashes and freezes after update"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93848#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [sna] Random X-Server crashes and freezes after update"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93848">bug 93848</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to M. G. from <a href="show_bug.cgi?id=93848#c9">comment #9</a>)
<span class="quote">> Created <span class=""><a href="attachment.cgi?id=121521" name="attach_121521" title="valgrind log">attachment 121521</a> <a href="attachment.cgi?id=121521&action=edit" title="valgrind log">[details]</a></span>
> valgrind log
>
> OK. I haven't had another crash yet (currently the X server crashes very
> rarely), but I see a lot of invalid read/writes with valgrind (see
> attachment). Are that critical errors that might lead to a segfault?</span >
Not yet. They appear to be noise from not compiling in valgrind support to the
ddx. You should see "SNA compiled for use with valgrind" in both the Xorg.0.log
and the valgrind output. The valgrind support adds markup to the driver
allocations and ioctls that valgrind by itself cannot see (and so tries to
avoid the false positives).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>