Identify what's causing segmentation fault in Yambo: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 15: | Line 15: | ||
## Use automatic parallelization, unset all parallel variable input | ## Use automatic parallelization, unset all parallel variable input | ||
## Run in serial | ## Run in serial | ||
# | # '''Optimization''': use a lower optimization level for example O1 or O0, by doing <code>./configure FCFLAGS="-O0" F77FLAGS="-O1"</code> | ||
# '''Compilers''': change C/Fortran compiler if it is possible, for example for intel fortran <code>./configure FC=ifort F77=ifort CC=icc</code> or for gfortran <code>./configure FC=gfortran F77=gfortran CC=gcc</code> | # '''Compilers''': change C/Fortran compiler if it is possible, for example for intel fortran <code>./configure FC=ifort F77=ifort CC=icc</code> or for gfortran <code>./configure FC=gfortran F77=gfortran CC=gcc</code> | ||
<br> | <br> | ||
'''Debugging the segmentation fault:''' | '''Debugging the segmentation fault:''' | ||
# Compile Yambo with checking options and run again your simulation, | # Compile Yambo with checking options and run again your simulation, report the result in the forum: | ||
## for | ## for g-fortran compiler <code>./configure FCFLAGS="-O1 -g -fcheck=all" UFLAGS="-O0 -g -fcheck=all" FFLAGS="-O1 -g -fcheck=all --enable-keep-src" | ||
## for | ## for intel fortran <code></code> |
Revision as of 17:30, 10 January 2021
There may be different reasons why the Yambo code generates segmentation faults in a run.
To help Yambo developers understand where the problem lies and help you, please follow the steps below.
If one of the step solves your problem and please report the result in the forum.
Rule out possible causes of the segmentation fault:
- GPU: are you running Yambo with GPU support? In this case try to recompile without
--enable-cuda
flag. If this solve the problem report your bug in the section Yambo on GPU machines otherwise to the next step. - OPEN-MP: compile and run Yambo without open-mp support, no
--enable-open-mp
flag in compilation andOMP_NUM_THREADS="1"
. - Internal Lapack/Blas: compile Yambo with internal Lapack/Blas libraries
--enable-int-linalg
in the configure. - Internal FFT: compile Yambo with internal FFT libraries
--enable-internal-fftsg
in the configure. - Scalapack: compile without Scalpack, unset the flag
--with-scalapack-libs
if you use it. - Parallelism
- Change the number of processors
- Use automatic parallelization, unset all parallel variable input
- Run in serial
- Optimization: use a lower optimization level for example O1 or O0, by doing
./configure FCFLAGS="-O0" F77FLAGS="-O1"
- Compilers: change C/Fortran compiler if it is possible, for example for intel fortran
./configure FC=ifort F77=ifort CC=icc
or for gfortran./configure FC=gfortran F77=gfortran CC=gcc
Debugging the segmentation fault:
- Compile Yambo with checking options and run again your simulation, report the result in the forum:
- for g-fortran compiler
./configure FCFLAGS="-O1 -g -fcheck=all" UFLAGS="-O0 -g -fcheck=all" FFLAGS="-O1 -g -fcheck=all --enable-keep-src"
- for intel fortran
- for g-fortran compiler