Hello,
We've encountered SIGSEGV in LAM's malloc() function problem with LAM
7.1.1.
The same application works fine with LAM 7.0. I know our application is
not
very clean regarding using realloc() ( we may give a null pointer to
realloc()).
Is there a way that we don't use LAM's wrapper functions for the
malloc() etc. ?
e.g. how do we build our applications not to use LAM's malloc() ?
We are using Redhat 9.0 with gcc 3.3, using TCP. The lam is not
configured with
"--with-purify".
Please help. here is the laminfo output:
531% laminfo
LAM/MPI: 7.1.1
Prefix: /ap/local/lam-7.1.1/LINUXM
Architecture: i686-pc-linux-gnu
Configured by: lily
Configured on: Mon Mar 21 14:57:06 CST 2005
Configure host: monk08
Memory manager: ptmalloc2
C bindings: yes
C++ bindings: yes
Fortran bindings: yes
C compiler: gcc
C++ compiler: g++
Fortran compiler: g77
Fortran symbols: double_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)
Regards,
Lily
|
