LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2005-01-06 08:09:57


This usually happens when the stdc++ libraries are not functioning
properly.

Can you run simple C++ programs with std::string? Does the
-D__interface switch that you used somehow impact the C++ standard
libraries?

Finally, what's the values of i, size, str[i], and c when mpif77 seg
faults?

On Jan 5, 2005, at 10:11 PM, Konstantin Skaburskas wrote:

>
> Hi,
>
> LAM configures, compiles and boots fine but wrapper compilers give
> setmentation fault (see below).
>
> My setup:
> - glibc 2.3.3-74, Intel Compilers v8.1, Fedora Core 3, kernel
> 2.6.9-1.667
> - LAM config:
> CC=icc
> CXX=icpc
> CXXFLAGS=-D__interface=myinterace
> FC=ifort
> export CC CXX CXXFLAGS FC
> ../lam-7.1.1/configure \
> --prefix=/usr/local/lam-7.1.1_intel \
> --with-trillium \
> --with-prefix-memcpy \
> --with-debug \
> --with-tv-debug \
> --enable-tv-dll-force \
> --enable-shared \
> --with-purify \
> --with-rsh="ssh -x"
>
> ...... eg. segmentation fault with mpif77:
>
> [ks] ~ > gdb mpif77
> GNU gdb Red Hat Linux (6.1post-1.20040607.41rh)
> (gdb) run
> Starting program: /usr/local/lam-7.1.1_intel/bin/mpif77
> [Thread debugging using libthread_db enabled]
> [New Thread 16384 (LWP 9425)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 9425)]
> 0x0804e354 in lam_wrap_split (str=@0xfefff108, c=32 ' ',
> out=@0xfeffef88)
> at ../../../lam-7.1.1/tools/wrappers/wrap_f77.cc:512
> 512 while (i < size && str[i] == c)
> (gdb) backtrace
> #0 0x0804e354 in lam_wrap_split (str=@0xfefff108, c=32 ' ',
> out=@0xfeffef88)
> at ../../../lam-7.1.1/tools/wrappers/wrap_f77.cc:512
> #1 0x0804bd1b in lam_wrap_get_compiler (env_list=@0xfefff0d8,
> default_comp=@0xfefff108,
> out=@0xfeffef88) at
> ../../../lam-7.1.1/tools/wrappers/wrap_f77.cc:173
> #2 0x0804f060 in lam_wrap_engine (argc=1, argv=0xfefff204,
> env_vars=@0xfefff0d8,
> default_compiler=@0xfefff108, want_cxx_includes=true,
> want_cxx_libs=false, want_f77_includes=true,
> extra_args=@0xfefff110) at
> ../../../lam-7.1.1/tools/wrappers/wrap_engine_f77.cc:68
> #3 0x080499a1 in main (argc=1, argv=0xfefff204) at
> ../../../lam-7.1.1/tools/wrappers/mpif77.cc:51
>
>
> Thank you in advance,
> Konstantin
>
> [ks] lam-7.1.1_intel > laminfo
> LAM/MPI: 7.1.1
> Prefix: /usr/local/lam-7.1.1_intel
> Architecture: i686-pc-linux-gnu
> Configured by: konstan
> Configured on: Thu Jan 6 03:17:16 EET 2005
> Configure host: ks.ce.ut.ee
> Memory manager: ptmalloc2
> C bindings: yes
> C++ bindings: yes
> Fortran bindings: yes
> C compiler: icc
> C++ compiler: icpc
> Fortran compiler: ifort
> Fortran symbols: underscore
> C profiling: yes
> C++ profiling: yes
> Fortran profiling: yes
> C++ exceptions: no
> Thread support: yes
> ROMIO support: yes
> IMPI support: no
> Debug support: yes
> Purify clean: yes
> SSI boot: globus (API v1.1, Module v0.6)
> SSI boot: rsh (API v1.1, Module v1.1)
> SSI boot: slurm (API v1.1, Module v1.0)
> SSI coll: lam_basic (API v1.1, Module v7.1)
> SSI coll: shmem (API v1.1, Module v1.0)
> SSI coll: smp (API v1.1, Module v1.2)
> SSI rpi: crtcp (API v1.1, Module v1.1)
> SSI rpi: lamd (API v1.0, Module v7.1)
> SSI rpi: sysv (API v1.0, Module v7.1)
> SSI rpi: tcp (API v1.0, Module v7.1)
> SSI rpi: usysv (API v1.0, Module v7.1)
> SSI cr: self (API v1.0, Module v1.0)
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>

-- 
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/