https://bugs.kde.org/show_bug.cgi?id=373288
--- Comment #1 from Philippe Waroquiers ---
Is this really related to Valgrind version 3.8.0 ?
This is obsolete/not maintained anymore.
Please upgrade to the last release (3.12.0) and retry.
Assuming you are using or have upgraded to 3.12.0 and problem still there,
please provide more information:
* which Linux distribution ?
* cat /proc/cpuinfo
* attach the output ofvalgrind -v -v -v -d -d -d date
Thanks
--
You are receiving this mail because:
You are watching all bug changes.