<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - llvmpipe crash in rendering on Atom" href="https://bugs.freedesktop.org/show_bug.cgi?id=94522#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - llvmpipe crash in rendering on Atom" href="https://bugs.freedesktop.org/show_bug.cgi?id=94522">bug 94522</a> from <a class="email" href="mailto:jfonseca@vmware.com" title="Jose Fonseca <jfonseca@vmware.com>"> Jose Fonseca</a> <pre>(In reply to comicfans44 from <a href="show_bug.cgi?id=94522#c16">comment #16</a>) > > How can I help to identify if this is the root cause ? I'm not familar with Wayland implementation details. The said memory must be allocated by one of the modules inside mesa/src/gallium/winsys/sw , but I'm not entirely sure which. IF you breakpoint llvmpipe_displaytarget_layout() and step through, you should be eable to see how this memory is being created. And you could then add some printfs or breakpoints to the deallocation. Another thing you could do is to do `cat /proc/PID/smaps` and see if / what sort of memory range the memory falls into. > if I build mesa with > address sanitizer ,can I force mesa not to use jit to let address sanitizer > to find if this is a heap-use-after-free ? If this is device memory, I doubt that sort of tools works. You could try valgrind.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>