<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - xf86-video-intel-2.99.907 segfaults while the machine is unattended"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73351#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - xf86-video-intel-2.99.907 segfaults while the machine is unattended"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73351">bug 73351</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 <a href="show_bug.cgi?id=73351#c18">comment #18</a>)
<span class="quote">> Created <span class=""><a href="attachment.cgi?id=92197" name="attach_92197" title="valgrind.log">attachment 92197</a> <a href="attachment.cgi?id=92197&action=edit" title="valgrind.log">[details]</a></span>
> valgrind.log
>
> Ok, it crashed again under valgrind (log attached). This time I have a lot
> more warnings, including many invalid writes. Using xf86-video-intel-git
> 2.99.907.16.g40beee9</span >
Apologies, it appears you compiled it without the valgrind headers and it
hasn't included the magic to suppress all the false positives.
<span class="quote">> Interestingly, it didn't print a stack trace into Xorg's log again; does
> valgrind somehow override Xorg's SIGSEGV handler?</span >
No. More likely it hit an assertion in that case...</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>