<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Android: i965/brw_draw affected by segfault in intel_disable_rb_aux_buffer()"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108782#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Android: i965/brw_draw affected by segfault in intel_disable_rb_aux_buffer()"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108782">bug 108782</a>
from <span class="vcard"><a class="email" href="mailto:lemody@gmail.com" title="Tapani Pälli <lemody@gmail.com>"> <span class="fn">Tapani Pälli</span></a>
</span></b>
<pre>(In reply to Tapani Pälli from <a href="show_bug.cgi?id=108782#c3">comment #3</a>)
<span class="quote">> (In reply to Mauro Rossi from <a href="show_bug.cgi?id=108782#c2">comment #2</a>)
> >
> > What should be the behavior in brw_draw.c @line 366 when irb->mt is null and
> > evaluation of irb->mt->bo causes the segfault?
> >
>
> That case should not happen, there should always be a miptree allocated to a
> render buffer. Something is broken already earlier if we can end up in such
> a situation.</span >
What I mean is that some of the miptree_create*() functions may have failed
already earlier (for some reason) and this is where the actual bug might be
lurking.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>