Bernard and I chatted off list -- looks like everything is ok. And
with that...
On Sep 14, 2004, at 4:50 PM, Borenstein, Bernard S wrote:
> I'm running on a Redhat 7.3 box (with 4.2.20 custom kernel), dual xeon
> 2.2 processors. I downloaded the latest LAM beta
>
> and built it with Portland Group 4.02. I then used this version of
> LAM to build the NASA OVERFLOW code. I've been using LAM
>
> for awhile and have not had any problems running OVERFLOW with LAM
> 7.0.x. The first problem I have is when I'm linking my
>
> OVEFLOW executable I get the error :
>
> pgf77-Warning-Unknown switch: --export-dynamic
>
> Running my newly built executable results in the following traceback
> near the beginning of my program execution :
>
> (gdb) bt
> #0 0x083edc53 in malloc_consolidate ()
> #1 0x083edae0 in _int_free ()
> #2 0x083ec960 in free ()
> #3 0x083fce38 in lam_ssi_rpi_usysv_destroy ()
> #4 0x083e000c in _mpi_req_destroy ()
> #5 0x083e0a86 in lam_send ()
> #6 0x083e5523 in MPI_Send ()
> #7 0x083cdf10 in mpi_send_ ()
> #8 0x08322d01 in fp_qsndrcv_ ()
> #9 0x003236a9 in ?? ()
> Cannot access memory at address 0x3
> (gdb) quit
>
> I then found that the configure script was using ptmalloc2 for
> memory. So I rebuilt LAM with the --with-memory-manager=none flag and
> Overflow
>
> then executed almost to completion, but died near the end with :
>
> (gdb) bt
> #0 0x400d976e in chunk_free () from /lib/libc.so.6
> #1 0x400d9548 in free () from /lib/libc.so.6
> #2 0x08412073 in al_free ()
> #3 0x083f1c89 in lam_ssi_rpi_cbuf_end ()
> #4 0x083e3231 in lam_ssi_rpi_base_close ()
> #5 0x083cb755 in MPI_Finalize ()
> #6 0x083c78b8 in mpi_finalize_ ()
> #7 0x0831e810 in end_mpi_ ()
> Cannot access memory at address 0x1
> (gdb)
>
> I'm attaching my config.log
>
> <<config.log.gz>>
>
> laminfo :
>
> LAM/MPI: 7.1b22
> Prefix: /fltapps/boeing/cfd/mpi/lam7.1b22_pgf
> Architecture: i686-pc-linux-gnu
> Configured by: borensbs
> Configured on: Mon Sep 13 10:02:40 PDT 2004
> Configure host: li13200
> Memory manager: none
> C bindings: yes
> C++ bindings: yes
> Fortran bindings: yes
> C compiler: pgcc
> C++ compiler: pgCC
> Fortran compiler: pgf77
> 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: no
> Purify clean: no
> 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)
>
> Hope you can help me with this.
>
> Bernie Borenstein
> The Boeing Company
> <config.log.gz>_______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
