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-
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
Using OpenMPI 4.0.1 and no configuration files of any kind on a linux
machine which shows 4 CPUS and 2 threads per CPU. When this is run:
mpirun --allow-run-as-root --oversubscribe -np 3
/usr/common/modules/el8/x86_64/software/q6/6.0.1-CentOS-vanilla/bin/qdynp
eq2.inp
it works and the expected 3
ed to lscpu). On machines with only 1 thread
> > per core, the cpu number is the number of physical cores.
> >
> > Thanks,
> > Collin
> >
> >
> > -Original Message-
> > From: users On Behalf Of David Mathog
> > via users
> > Se
