<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#c4">Comment # 4</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:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to Grazvydas Ignotas from <a href="show_bug.cgi?id=99060#c3">comment #3</a>)
<span class="quote">> xserver-xorg-core-dbg is installed, but for some reason valgrind doesn't
> like those debug symbols (see it's complaints ant the beginning of the log).</span >
Looks like the xserver-xorg-core-dbg package is missing the debugging symbols
for
/usr/lib/xorg/Xorg.
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 class="quote">> I've tested this on iGPU with xf86-video-intel and it doesn't trigger the
> issue.</span >
Was DRI3 enabled when testing that as well?
<span class="quote">> As modesetting is also fine, it strongly suggests it's amdgpu that's
> somehow provoking it.</span >
valgrind doesn't complain either in that case?</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>