https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #8 from Joost VandeVondele <joost.vandevond...@mat.ethz.ch> ---
The failures are observed on RedHatEnterpriseServer Release: 6.7
over the weekend, I have been running valgrind with as an argument essentially
just a start of the relevant binary (and have it print the version number).
With >200000 runs (10s each) I had no failure. This is on different machine
with Redhat 7.2
I'll try something similar on the other machine, but the failure is not so easy
to trigger, seemingly.
Dynamic libraries in my case are few, and standard I suppose:
> ldd /data/vjoost/clean/cp2k/cp2k/exe/local_valgrind/cp2k.sdbg
linux-vdso.so.1 => (0x00007ffe09f0d000)
libstdc++.so.6 =>
/data/vjoost/toolchain-r16447/install/lib64/libstdc++.so.6 (0x00007f7d5a890000)
libgfortran.so.3 =>
/data/vjoost/toolchain-r16447/install/lib64/libgfortran.so.3
(0x00007f7d5a56f000)
libm.so.6 => /lib64/libm.so.6 (0x0000003233200000)
libgcc_s.so.1 => /data/vjoost/toolchain-r16447/install/lib64/libgcc_s.so.1
(0x00007f7d5a33c000)
libquadmath.so.0 =>
/data/vjoost/toolchain-r16447/install/lib64/libquadmath.so.0
(0x00007f7d5a0fd000)
libc.so.6 => /lib64/libc.so.6 (0x0000003232e00000)
/lib64/ld-linux-x86-64.so.2 (0x0000003232a00000)
There are many more static libraries involved, and all are compiled with debug
info. The binary is also large (~142Mb).
--
You are receiving this mail because:
You are watching all bug changes.
