PETSc and gfortran

Satish Balay balay at mcs.anl.gov
Wed Jan 10 17:46:10 CST 2007


BUS error is a bit suspicious. What can you send the output from all
of the following commands..

cd src/ksp/ksp/examples/tutorials
make ex2f
./ex2f
gdb ex2f
(gdb) run


Satish

On Wed, 10 Jan 2007, Paul T. Bauman wrote:

> Yes, example ex5f broke in the exact same way. Note the preceding c/c++
> examples worked perfectly.  How would you suggest I proceed?  Thanks,
> 
> Paul
> 
> Satish Balay wrote:
> > Can you reproduce this with a PETSc example?
> > 
> > make test
> > 
> > Satish
> > 
> > On Wed, 10 Jan 2007, Paul T. Bauman wrote:
> > 
> >   
> > > Hello,
> > > 
> > > Has anyone had any experience using PETSc and gfortran together?  My code
> > > compiles, but when I run it, it crashes with the following error (mac
> > > Tiger
> > > 10.4.8, power pc, latest build of gfortran, MPICH2, petsc 2.3.2):
> > > 
> > > [0]PETSC ERROR:
> > > ------------------------------------------------------------------------
> > > [0]PETSC ERROR: Caught signal number 10 BUS: Bus Error, possibly illegal
> > > memory access
> > > [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
> > > [0]PETSC ERROR: or see
> > > http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC
> > > ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple to
> > > find
> > > memory corruption errors
> > > [0]PETSC ERROR: likely location of problem given in stack below
> > > [0]PETSC ERROR: ---------------------  Stack Frames
> > > ------------------------------------
> > > [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not
> > > available,
> > > [0]PETSC ERROR:       INSTEAD the line number of the start of the function
> > > [0]PETSC ERROR:       is given.
> > > [0]PETSC ERROR: --------------------- Error Message
> > > ------------------------------------
> > > [0]PETSC ERROR: Signal received!
> > > [0]PETSC ERROR:
> > > ------------------------------------------------------------------------
> > > [0]PETSC ERROR: Petsc Release Version 2.3.2, Patch 8, Tue Jan  2 14:33:59
> > > PST
> > > 2007 HG revision: ebeddcedcc065e32fc252af32cf1d01ed4fc7a80
> > > [0]PETSC ERROR: See docs/changes/index.html for recent updates.
> > > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.
> > > [0]PETSC ERROR: See docs/index.html for manual pages.
> > > [0]PETSC ERROR:
> > > ------------------------------------------------------------------------
> > > [0]PETSC ERROR: EXEC/shrink_tao on a Apple_Pow named
> > > dhcp-67-30.ices.utexas.edu by pbauman Wed Jan 10 17:20:03 2007
> > > [0]PETSC ERROR: Libraries linked from
> > > /Users/pbauman/LIBRARIES/PETSC/petsc-2.3.2-p8/lib/Apple_PowerPC_Tiger_Debug
> > > [0]PETSC ERROR: Configure run at Tue Jan  9 15:42:42 2007
> > > [0]PETSC ERROR: Configure options --with-shared=0 --with-clanguage=C++
> > > 
> > > --with-mpi-dir=/Users/pbauman/LIBRARIES/MPICH/mpich2-1.0.5_Apple_PowerPC_Tiger_gcc_gfortran
> > > 
> > > --with-blas-lapack-dir=/Users/pbauman/LIBRARIES/PETSC/petsc-2.3.2-p8/externalpackages/fblaslapack/Apple_PowerPC_Tiger_Debug/
> > > [0]PETSC ERROR:
> > > ------------------------------------------------------------------------
> > > [0]PETSC ERROR: User provided function() line 0 in unknown directory
> > > unknown
> > > file
> > > [cli_0]: aborting job:
> > > application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0
> > > rank 0 in job 2  dhcp-67-30.ices.utexas.edu_50482   caused collective
> > > abort of
> > > all ranks
> > >  exit status of rank 0: return code 59
> > > make: *** [run_shrink_tao_tr] Error 59
> > > 
> > > This happens at the very beginning of the code (I put a write statement in
> > > at
> > > the first line of the program and nothing came out).  This code runs
> > > successfully on linux with intel compilers. I'm sure the problem is
> > > somehow
> > > with gfortran/my build, I'm just not sure where to begin with this kind of
> > > problem, so I thought I'd see if anyone had a similar experience.
> > > 
> > > Thanks,
> > > 
> > > Paul
> > > 
> > > 
> > >     
> 
> 




More information about the petsc-users mailing list