https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #25 from Eric Chamberland ---
FWIW, the svn version of valgrind didn't produced any blockSane assertion last
night, but since it was randomly happening, we have to let go some days to see
if this bug is definitely not occurring again.
Thank
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #24 from Eric Chamberland ---
Created attachment 101660
--> https://bugs.kde.org/attachment.cgi?id=101660&action=edit
valgrind launched with -v -v -v -d -d -d
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #23 from Eric Chamberland ---
Thanks Joost for these informations: In fact, we will upgrade the os when
possible...
This morning, I have 4 (different) failing tests.
I launched 3.11.0 with -v -v -v -d -d -d, please see valgrind_with_vvvddd
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #21 from Eric Chamberland ---
Finally I got not 6 but 8 failing tests (wrote the report before they all
completed...)
I have 7 different libraries where valgrind hangs:
#1:
--17999-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #18 from Eric Chamberland ---
Some other informations:
Distribution: openSUSE 12.3
Kernel: cat /proc/version
Linux version 3.7.10-1.45-desktop (geeko@buildhost) (gcc version 4.7.2 20130108
[gcc-4_7-branch revision 195012] (SUSE Linux) ) #1
https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #17 from Eric Chamberland ---
(copied from valgrind-users list following Julian Seward request)
Hi,
I recently upgraded to valgrind 3.11.0 (was 3.8.1 before).
I also upgraded Intel MKL to the 2015 version.
We use valgrind since 2011-10-27
https://bugs.kde.org/show_bug.cgi?id=356457
Eric Chamberland changed:
What|Removed |Added
CC||eric.chamberl...@gmail.com
--- Comment #16 f
