On 30-Apr-2019 11:39, George Bosilca wrote:
Depending on the alignment of the different types there might be small
holes in the low-level headers we exchange between processes It should
not
be a concern for users.
valgrind should not stop on the first detected issue except
if --exit-on-first-e
Depending on the alignment of the different types there might be small
holes in the low-level headers we exchange between processes It should not
be a concern for users.
valgrind should not stop on the first detected issue except
if --exit-on-first-error has been provided (the default value should
Attempting to debug a complex program (99.9% of which is others' code)
which stops running when run in valgrind as follows:
mpirun -np 10 \
--hostfile /usr/common/etc/openmpi.machines.LINUX_INTEL_newsaf_rev2 \
--mca plm_rsh_agent rsh \
/usr/bin/valgrind \
--leak-check=full \
--leak-
