[mvapich-discuss] Problem at OSC with mvapich debugging

[Doug Johnson]

Tim,

You would probably be better off contacting oschelp at osc.edu for help
with this problem.  

Doug Johnson


At Fri, 18 Dec 2009 16:20:36 -0500,
Tim Hartley wrote:
> 
> Hi,
> 
> I'm trying to debug my application with gdb, but am having trouble
> getting the debugger to start with OSC's installed mvapich.
> 
> I'm using the module mvapich-1.1-gnu on OSC's glenn cluster.
> 
> Here are the installation details:
> $ mpicxx -v
> mpiCC for 1.2.7 (release) of : 2005/06/22 16:33:49
> Using built-in specs.
> Target: x86_64-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-libgcj-multifile
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi --enable-plugin
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --with-cpu=generic --host=x86_64-redhat-linux
> Thread model: posix
> gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)
>  /usr/libexec/gcc/x86_64-redhat-linux/4.1.2/collect2 --eh-frame-hdr -m
> elf_x86_64 --hash-style=gnu -dynamic-linker
> /lib64/ld-linux-x86-64.so.2
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/crt1.o
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/crti.o
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/crtbegin.o
> -L/usr/local/mpi/mvapich-1.1-gnu/lib/shared
> -L/usr/local/mpi/mvapich-1.1-gnu/lib -L/usr/lib64
> -L/home/osu4771/.upak/commons/lib -L.
> -L/usr/lib/gcc/x86_64-redhat-linux/4.1.2
> -L/usr/lib/gcc/x86_64-redhat-linux/4.1.2
> -L/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64
> -L/lib/../lib64 -L/usr/lib/../lib64 -rpath-link
> /usr/local/mpi/mvapich-1.1-gnu/lib/shared -lpmpich++ -lmpich
> -rpath=/usr/lib64 -libverbs -libumad -lpthread -lpthread -lrt -lstdc++
> -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/crtend.o
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/crtn.o
> /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/crt1.o: In
> function `_start':
> (.text+0x20): undefined reference to `main'
> collect2: ld returned 1 exit status
> 
> Here is the error message:
> $ mpirun_rsh -debug -np 1 -hostfile /tmp/DCMPI_IPOl0k /home/osu4771/app
> debug enabled !
> RSH/SSH command failed!: No such file or directory
> 
> Child exited abnormally!
> Killing remote processes...ModuleCmd_Load.c(200):ERROR:105: Unable to
> locate a modulefile for 'cuda'
> DONE
> 
> This is with an extremely simple application.
> 
> Do I need to spin my own mvapich install, or ask for the OSC guys to
> rebuild that module?
> 
> Thanks,
> Tim
> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss