<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - memory corruption after running INSIDE"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99060#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - memory corruption after running INSIDE"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99060">bug 99060</a>
from <span class="vcard"><a class="email" href="mailto:notasas@gmail.com" title="Grazvydas Ignotas <notasas@gmail.com>"> <span class="fn">Grazvydas Ignotas</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=99060#c4">comment #4</a>)
<span class="quote">>
> Any chance you can build the xorg-server source package locally and replace
> /usr/lib/xorg/Xorg with the unstripped version from your build? It's hard to
> make sense of the valgrind output without line numbers for the Xorg entries.</span >
I'll try that after work.
<span class="quote">> > I've tested this on iGPU with xf86-video-intel and it doesn't trigger the
> > issue.
>
> Was DRI3 enabled when testing that as well?</span >
Yes.
<span class="quote">> > As modesetting is also fine, it strongly suggests it's amdgpu that's
> > somehow provoking it.
>
> valgrind doesn't complain either in that case?</span >
No, pretty much clean output.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>