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#36844 - [valgrind] lacking lock xaddb support.
Attached to Project:
Arch Linux
Opened by Emmanuel Thomé (ethome) - Monday, 09 September 2013, 23:18 GMT
Last edited by Allan McRae (Allan) - Sunday, 15 September 2013, 10:03 GMT
Opened by Emmanuel Thomé (ethome) - Monday, 09 September 2013, 23:18 GMT
Last edited by Allan McRae (Allan) - Sunday, 15 September 2013, 10:03 GMT
|
DetailsDescription:
The current release of valgrind has a regression compared to pre-3.8.0, since the "lock xaddb" instruction is not recognized (whenever you do sync_add_and_fetch, this is likely to show up). This is fixed upstream, but no fresher release exists yet, which is a pity since this bug is 1-yr old... https://bugs.kde.org/show_bug.cgi?id=307106 The valgrind BTS has a patch by Jakub Jelinek for this. Would it be possible to update the archlinux package with this patch ? Thanks. Steps to reproduce: int main (int argc, char **argv) { asm("xaddb %dl,(%rax)"); return 0; } valgrind ./a.out |
This task depends upon
Closed by Allan McRae (Allan)
Sunday, 15 September 2013, 10:03 GMT
Reason for closing: Fixed
Additional comments about closing: valgrind-3.8.1-4
Sunday, 15 September 2013, 10:03 GMT
Reason for closing: Fixed
Additional comments about closing: valgrind-3.8.1-4