https://bugs.freedesktop.org/show_bug.cgi?id=94522
--- Comment #17 from Jose Fonseca <jfons...@vmware.com> ---
(In reply to comicfans44 from comment #16)
>
> 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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
