[r...@gc07 bin]# time /root/my/mvapich/bin/mpirun_rsh -np 1 -hostfile
/root/my/NPB3.3/NPB3.3-MPI/host.mpi /root/my/NPB3.3/NPB3.3-MPI/bin/is.C.1


The above command running NPB3.IS.C gives correct result. But following
command fails. Lackey gives similar error message.



[r...@gc07 bin]# time /root/my/mvapich/bin/mpirun_rsh -np 1 -hostfile
/root/my/NPB3.3/NPB3.3-MPI/host.mpi ./valgrind -d -d -d -d --tool=none
/root/my/NPB3.3/NPB3.3-MPI/bin/is.C.1
Exit code -5 signaled from gc07
Killing remote processes...--16378:1:debuglog DebugLog system started by
Stage 1, level 4 logging requested
--16378:1:launcher tool 'none' requested
--16378:2:launcher selecting platform for
'/root/my/NPB3.3/NPB3.3-MPI/bin/is.C.1'
--16378:2:launcher selecting platform for
'/root/my/NPB3.3/NPB3.3-MPI/bin/is.C.1'
--16378:2:launcher opened '/root/my/NPB3.3/NPB3.3-MPI/bin/is.C.1'
--16378:2:launcher read 4096 bytes from
'/root/my/NPB3.3/NPB3.3-MPI/bin/is.C.1'
--16378:2:launcher selected platform 'amd64-linux'
--16378:1:launcher selected platform 'amd64-linux'
--16378:1:launcher launching
/home/yuhuang/valgrind-3.6.0/bin/lib/valgrind/none-amd64-linux
--16378:1:debuglog DebugLog system started by Stage 2 (main), level 4
logging requested
--16378:1:main Welcome to Valgrind version 3.6.0 debug logging
--16378:1:main Checking current stack is plausible
--16378:1:main Checking initial stack was noted
--16378:1:main Starting the address space manager
--16378:2:aspacem sp_at_startup = 0x7fff43bc81d0 (supplied)
--16378:2:aspacem minAddr = 0x0004000000 (computed)
--16378:2:aspacem maxAddr = 0x07ffffffff (computed)
--16378:2:aspacem cStart = 0x0004000000 (computed)
--16378:2:aspacem vStart = 0x0402000000 (computed)
--16378:2:aspacem suggested_clstack_top = 0x07ff000fff (computed)
--16378:2:aspacem <<< SHOW_SEGMENTS: Initial layout (5 segments, 0 segnames)
--16378:2:aspacem 0: RSVN 0000000000-0003ffffff 64m ----- SmFixed
--16378:2:aspacem 1: 0004000000-0401ffffff 16352m
--16378:2:aspacem 2: RSVN 0402000000-0402000fff 4096 ----- SmFixed
--16378:2:aspacem 3: 0402001000-07ffffffff 16351m
--16378:2:aspacem 4: RSVN 0800000000-ffffffffffffffff 16383e ----- SmFixed
--16378:2:aspacem >>>
--16378:2:aspacem Reading /proc/self/maps
--16378:2:aspacem <<< SHOW_SEGMENTS: With contents of /proc/self/maps
(16 segments, 1 segnames)
--16378:2:aspacem ( 0)
/home/yuhuang/valgrind-3.6.0/bin/lib/valgrind/none-amd64-linux
--16378:2:aspacem 0: RSVN 0000000000-0003ffffff 64m ----- SmFixed
--16378:2:aspacem 1: 0004000000-0037ffffff 832m
--16378:2:aspacem 2: FILE 0038000000-0038217fff 2195456 r-x-- d=0x015
i=5767906 o=2097152 (0)
--16378:2:aspacem 3: 0038218000-0038416fff 2093056
--16378:2:aspacem 4: FILE 0038417000-0038419fff 12288 rw--- d=0x015
i=5767906 o=4288512 (0)
--16378:2:aspacem 5: ANON 003841a000-0038f88fff 11m rw---
--16378:2:aspacem 6: 0038f89000-0401ffffff 15504m
--16378:2:aspacem 7: RSVN 0402000000-0402000fff 4096 ----- SmFixed
--16378:2:aspacem 8: 0402001000-07ffffffff 16351m
--16378:2:aspacem 9: RSVN 0800000000-7fff43bb3fff 131037g ----- SmFixed
--16378:2:aspacem 10: ANON 7fff43bb4000-7fff43bc8fff 86016 rw---
--16378:2:aspacem 11: RSVN 7fff43bc9000-7fff43bfefff 221184 ----- SmFixed
--16378:2:aspacem 12: ANON 7fff43bff000-7fff43bfffff 4096 r-x--
--16378:2:aspacem 13: RSVN 7fff43c00000-ffffffffff5fffff 16383e -----
SmFixed
--16378:2:aspacem 14: ANON ffffffffff600000-ffffffffff600fff 4096 r-x--
--16378:2:aspacem 15: RSVN ffffffffff601000-ffffffffffffffff 9m -----
SmFixed
--16378:2:aspacem >>>
--16378:1:main Address space manager is running
--16378:1:main Starting the dynamic memory manager
--16378:1:mallocfr newSuperblock at 0x402001000 (pszB 4194272) owner
VALGRIND/tool
--16378:1:main Dynamic memory manager is running
--16378:1:main Initialise m_debuginfo
--16378:1:main VG_(libdir) = /home/yuhuang/valgrind-3.6.0/bin/lib/valgrind
--16378:1:main Getting launcher's name ...
--16378:1:main ... /home/yuhuang/valgrind-3.6.0/bin/bin/valgrind
--16378:1:main Get hardware capabilities ...
--16378:1:main ... arch = AMD64, hwcaps = amd64-sse3-cx16
--16378:1:main Getting the working directory at startup
--16378:1:main ... /home/yuhuang/valgrind-3.6.0/bin/bin
--16378:1:main Split up command line
--16378:1:main (early_) Process Valgrind's command line options
--16378:1:main Create initial image
--16378:1:initimg Loading client
valgrind: mmap(0x708000, 2416074752) failed in UME with error 22
(Invalid argument).
valgrind: this can be caused by executables with very large text, data
or bss segments.
MPI process terminated unexpectedly


DONE

real 0m1.097s
user 0m0.011s
sys 0m0.002s
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to