Arch Linux

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!
Tasklist

FS#41696 - [valgrind] Add patch for XABORT

Attached to Project: Arch Linux
Opened by Åsmund Ervik (AsmundEr) - Tuesday, 26 August 2014, 09:28 GMT
Last edited by Anatol Pomozov (anatolik) - Wednesday, 10 September 2014, 17:34 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

With recent CPUs supporting AVX and recent versions of glibc, valgrind 3.9.0 does not work since it encounters an illegal instruction at the very start of the program, and is then unable to continue. This is due to an unimplemented (in valgrind) instruction called XABORT. The error message looks like this:

==9994== valgrind: Unrecognised instruction at address 0x71bbfb0.
==9994== at 0x71BBFB0: __lll_trylock_elision (in /usr/lib/libpthread-2.19.so)
==9994== by 0x71B4BE3: pthread_mutex_trylock (in /usr/lib/libpthread-2.19.so)
==9994== by 0x7B33E10: ??? (in /usr/lib/libgfortran.so.3.0.0)
==9994== by 0x7B32749: ??? (in /usr/lib/libgfortran.so.3.0.0)

There is a patch for this issue located here: http://valgrind.10908.n7.nabble.com/vex-r2800-trunk-priv-guest-amd64-toIR-c-td48073.html

Please add this patch, it doesn't look like there is a new valgrind release coming up soon.

Additional info:
* valgrind 3.9.0

Steps to reproduce:
* compile code with recent glibc on CPU supporting AVX
* try to check code with valgrind
* error occurs at the very beginning of execution
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Wednesday, 10 September 2014, 17:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.9.0-5
Comment by Anatol Pomozov (anatolik) - Tuesday, 02 September 2014, 23:18 GMT
It makes sense to add the patch. Thanks for the report.

I just released 3.9.0-5 to [testing], please download it from there and let me know if there are any issues with new version of valgrind.
Comment by Åsmund Ervik (AsmundEr) - Wednesday, 03 September 2014, 07:33 GMT
I just downloaded the latest version from [testing], and it works perfectly for me. Thank you very much.
Comment by Anatol Pomozov (anatolik) - Wednesday, 10 September 2014, 17:34 GMT
All right, closing it as fixed.

I looked through the development history for valgrind and they have numerous changes that improve latest hardware support (new ops like transactional memory). It would be really good idea to put pressure on valgrind maintainers to release a new version with those changes.

Loading...