http://bugzilla.opensuse.org/show_bug.cgi?id=1173355 Bug ID: 1173355 Summary: X11:XOrg/Mesa: Enable valgrind support (-Dvalgrind=true) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs@suse.de Reporter: rverschelde@gmail.com QA Contact: gfx-bugs@suse.de CC: sndirsch@suse.com Found By: --- Blocker: --- As far I can see in the Mesa spec file [0], it does not build with `valgrind` as a BuildRequires, so openSUSE's Mesa will generate thousands of irrelevant errors when trying to debug an OpenGL or Vulkan application with valgrind. See e.g. https://www.phoronix.com/scan.php?page=news_item&px=MTQzNjk or https://twitter.com/Akien/status/1141414741346312193 for context on this issue. Several distros have enabled valgrind support in Mesa in recent years: - Fedora: https://src.fedoraproject.org/rpms/mesa/c/37749951bc4d289a522ca332b3cc9cada8... - Arch: https://bugs.archlinux.org/task/62943 - Mageia: https://ml.mageia.org/l/arc/dev/2019-07/msg00003.html (I'm a Mageia packager) I would recommend doing the same in openSUSE. I discussed it with Mesa developers on #dri-devel back in mid-2019 before enabling it in Mageia, and they confirmed that building Mesa with valgrind support was recommended and should not have a significant performance impact. For context, I recommended the same to the Debian Mesa maintainer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890846#19 To enable it in the openSUSE spec, this should do the trick: ``` BuildRequires: valgrind ... %meson \ ... -Dvalgrind=true \ ... ``` -- You are receiving this mail because: You are on the CC list for the bug.