On Tue, Jun 20, 2017 at 03:10:29PM -0500, Frank Loeffler wrote:
These are results with the change: both 1 and 2-process testsuites:mpirun noticed that process rank 0 with PID 0 on node spine exited on signal 11 (Segmentation fault).
gdb tells me: #0 NaNChecker::CHECK_DATA<double> () at /home/knarf/TMP/configs/L2/build/NaNChecker/NaNCheck.cc:644#1 0x00007ffff35b36b6 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1 #2 0x00007ffff6eb9494 in start_thread (arg=0x7fffd4031700) at pthread_create.c:333 #3 0x00007ffff30cfaff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
So the segfault actually happens in NanChecker, trying to access _data[i=0:nelems] in CHECK_DATA.
Is SphericalHarmonicReconGen doing something strange with the Cactus infrastructure, or does this more point to some memory garbage?
Frank
signature.asc
Description: Digital signature
_______________________________________________ Users mailing list [email protected] http://lists.einsteintoolkit.org/mailman/listinfo/users
