[petsc-dev] [mpich-trac] #2321: mpich-3.2 is not valgrind clean with petsc examples
mpich
noreply at mpich.org
Fri Dec 18 14:32:41 CST 2015
#2321: mpich-3.2 is not valgrind clean with petsc examples
-------------------+-------------------
Reporter: balay | Type: bug
Status: new | Priority: major
Milestone: | Component: mpich
Keywords: |
-------------------+-------------------
When petsc switched from 3.1.3 to 3.2 - we started seeing valgrind
messages from MPICH.
Could you take a look at this? I can help with running petsc examples that
produce these messages.
valgrind clean log with mpich-3.1.3
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/12/12
/examples_master_arch-linux-pkgs-valgrind_grind.log
same build log with mpich-3.2
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/12/13
/examples_master_arch-linux-pkgs-valgrind_grind.log
mpich configured with:
{{{
./configure --prefix=/sandbox/petsc/petsc.clone/arch-linux-pkgs-valgrind
MAKE=/usr/bin/make --libdir=/sandbox/petsc/petsc.clone/arch-linux-pkgs-
valgrind/lib CC="gcc" CFLAGS="-fPIC -g3" AR="/usr/bin/ar" ARFLAGS="cr"
CXX="g++" CXXFLAGS="-g -fPIC -std=c++11" F77="gfortran" FFLAGS="-fPIC
-ffree-line-length-0 -g" FC="gfortran" FCFLAGS="-fPIC -ffree-line-length-0
-g" --enable-shared --with-device=ch3:sock --with-pm=hydra --enable-
fast=no --enable-g=meminit
}}}
--
Ticket URL: <http://trac.mpich.org/projects/mpich/ticket/2321>
More information about the petsc-dev
mailing list