Identify what's causing segmentation fault in Yambo: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
# '''OPEN-MP'''. Try to compile and run without open-mp support, no <code>--enable-open-mp</code> flag in compilation and <code>OMP_NUM_THREADS="1"</code>. | # '''OPEN-MP'''. Try to compile and run without open-mp support, no <code>--enable-open-mp</code> flag in compilation and <code>OMP_NUM_THREADS="1"</code>. | ||
# '''Internal Lapack/Blas''' Try to compile | # '''Internal Lapack/Blas''' Try to compile with internal Lapack/Blas libraries <code>--enable-int-linalg</code> in the configure. | ||
# '''Internal FFT''' Try to compile with internal FFT libraries <code>--enable-internal-fftsg</code> in the configure |
Revision as of 17:11, 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,
see if they solve your problem and then 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. Try to compile and run without open-mp support, no
--enable-open-mp
flag in compilation andOMP_NUM_THREADS="1"
.
- Internal Lapack/Blas Try to compile with internal Lapack/Blas libraries
--enable-int-linalg
in the configure.
- Internal FFT Try to compile with internal FFT libraries
--enable-internal-fftsg
in the configure