Here's the back trace:
(gdb) run
Starting program: /h/suzu0037/Local/MPI/lam/bin/lamexec
[New Thread 16384 (LWP 25873)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 25873)]
0x4003c156 in _ksig_init () from /h/suzu0037/Local/MPI/lam/lib/liblam.so.0
(gdb) where
#0 0x4003c156 in _ksig_init () from
/h/suzu0037/Local/MPI/lam/lib/liblam.so.0
#1 0x4003b908 in kinit () from /h/suzu0037/Local/MPI/lam/lib/liblam.so.0
#2 0x080495ca in main ()
#3 0x420158f7 in __libc_start_main () from /lib/i686/libc.so.6
I used Intel compiler 8.1 (icc,icpc,ifort) with "-O3 -xW -tpp7" compiler
flag. The configuration options are
./configure --prefix=$HOME/Local/MPI/lam \
--enable-shared=yes \
--disable-tv \
--disable-tv-queue \
--with-profiling \
--with-threads=posix \
--with-purify \
--with-trillium \
--with-rsh=ssh
I can boot LAM and use mpirun without any problem. Will this help?
Ryuta
Jeff Squyres wrote:
> No, this is not a known problem.
>
> Can you be more specific? What version of LAM are you using? Can you
> load up the corefiles in a debugger and send a back trace of where the
> problem occurs?
>
>
> On Nov 12, 2004, at 12:11 PM, Ryuta Suzuki wrote:
>
>> Has anybody experienced seg fault in lamexec and lamgrow? I'm using
>> Intel compiler 8.1 and gcc 3.4 is installed in the system. I just got
>> seg fault immediately after I invoke lamexec and lamgrow.
>> _______________________________________________
>> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>>
>
|
