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#55571 - [valgrind] --xml-socket argument doesn't work correctly
Attached to Project:
Arch Linux
Opened by Daniel Otero (canu7) - Saturday, 09 September 2017, 21:59 GMT
Last edited by Levente Polyak (anthraxx) - Thursday, 21 December 2017, 19:36 GMT
Opened by Daniel Otero (canu7) - Saturday, 09 September 2017, 21:59 GMT
Last edited by Levente Polyak (anthraxx) - Thursday, 21 December 2017, 19:36 GMT
|
DetailsThe Valgrind 3.13 version has a bug that breaks the "--xml-socket" argument functionality.
This bug was already reported and fixed mainstream (https://bugs.kde.org/show_bug.cgi?id=382998), but as the release schedule of Valgrind seems rather slow (once a year?) and other packages rely on this functionality (I'm affected because of QtCreator use of memcheck), can we add the patch manually in the PKGBUILD? The patch is trivial and just need to be removed in the following release. I tested it myself and worked without issues. Thank you! |
This task depends upon
Closed by Levente Polyak (anthraxx)
Thursday, 21 December 2017, 19:36 GMT
Reason for closing: Fixed
Additional comments about closing: 3.13.0-5
Thursday, 21 December 2017, 19:36 GMT
Reason for closing: Fixed
Additional comments about closing: 3.13.0-5
fix-xml-socket.patch