Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#62943 - [mesa] Enable valgrind support
Attached to Project:
Arch Linux
Opened by Link Mauve (linkmauve) - Wednesday, 19 June 2019, 15:39 GMT
Last edited by Laurent Carlier (lordheavy) - Wednesday, 19 June 2019, 16:15 GMT
Opened by Link Mauve (linkmauve) - Wednesday, 19 June 2019, 15:39 GMT
Last edited by Laurent Carlier (lordheavy) - Wednesday, 19 June 2019, 16:15 GMT
|
DetailsDescription:
Mesa builds with -D valgrind=false since https://git.archlinux.org/svntogit/packages.git/commit/trunk/PKGBUILD?h=packages/mesa&id=3a5dd7127b0dc49d74328131c3c190a9142110bb with no explanation. This makes valgrind produce a lot of unnecessary warnings since it doesn’t know about the various ioctl()s used by Mesa drivers, preventing the user from finding actual memory issues in their programs. Additional info: * package version(s) 19.1.0-1 * config and/or log files etc. N/A * link to upstream bug report, if any N/A Steps to reproduce: - Install any program using OpenGL or Vulkan. - Run it under valgrind. Observe how many useless warnings there are, when Mesa isn’t built with -D valgrind=true. |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Wednesday, 19 June 2019, 16:15 GMT
Reason for closing: Fixed
Additional comments about closing: mesa-19.1.0-2
Wednesday, 19 June 2019, 16:15 GMT
Reason for closing: Fixed
Additional comments about closing: mesa-19.1.0-2