Gus Correa <g...@ldeo.columbia.edu> writes: > Hi Giacomo > > Some programs fail with segmentation fault > because the stack size is too small.
Yes, the default for Intel Fortran is to allocate large-ish amounts on the stack, which may matter when the compiled program runs. However, look at the backtrace. It's apparently coming from the loader, so something is pretty screwed up, though I can't guess what. It would help to have debugging symbols; always use at least -g and have GNU/Linux distribution debuginfo packages to hand. [Probably not relevant in this case, but I try to solve problems with the Intel compiler and MPI (sorry Jeff et al) by persuading users to avoid them. GCC is more reliable in my experience, and the story about its supposedly poor code generation isn't supported by experiment (if that counts for anything these days).] > [But others because of bugs in memory allocation/management, etc.] > > Have you tried > > ulimit -s unlimited > > before you run the program? > > Are you using a single machine or a cluster? > If you're using infiniband you may need also to make the locked memory > unlimited: > > ulimit -l unlimited > > I hope this helps, > Gus Correa > > On 05/05/2016 05:15 AM, Giacomo Rossi wrote: >> gdb /opt/openmpi/1.10.2/intel/16.0.3/bin/mpif90 >> GNU gdb (GDB) 7.11 >> Copyright (C) 2016 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> <http://gnu.org/licenses/gpl.html> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. Type "show copying" >> and "show warranty" for details. >> This GDB was configured as "x86_64-pc-linux-gnu". >> Type "show configuration" for configuration details. >> For bug reporting instructions, please see: >> <http://www.gnu.org/software/gdb/bugs/>. >> Find the GDB manual and other documentation resources online at: >> <http://www.gnu.org/software/gdb/documentation/>. >> For help, type "help". >> Type "apropos word" to search for commands related to "word"... >> Reading symbols from /opt/openmpi/1.10.2/intel/16.0.3/bin/mpif90...(no >> debugging symbols found)...done. >> (gdb) r -v >> Starting program: /opt/openmpi/1.10.2/intel/16.0.3/bin/mpif90 -v >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x00007ffff6858f38 in ?? () >> (gdb) bt >> #0 0x00007ffff6858f38 in ?? () >> #1 0x00007ffff7de5828 in _dl_relocate_object () from >> /lib64/ld-linux-x86-64.so.2 >> #2 0x00007ffff7ddcfa3 in dl_main () from /lib64/ld-linux-x86-64.so.2 >> #3 0x00007ffff7df029c in _dl_sysdep_start () from >> /lib64/ld-linux-x86-64.so.2 >> #4 0x00007ffff7dddd4a in _dl_start () from /lib64/ld-linux-x86-64.so.2 >> #5 0x00007ffff7dd9d98 in _start () from /lib64/ld-linux-x86-64.so.2 >> #6 0x0000000000000002 in ?? () >> #7 0x00007fffffffaa8a in ?? () >> #8 0x00007fffffffaab6 in ?? () >> #9 0x0000000000000000 in ?? () >> >> Giacomo Rossi Ph.D., Space Engineer >> >> Research Fellow at Dept. of Mechanical and Aerospace Engineering, >> "Sapienza" University of Rome >> *p: *(+39) 0692927207 | *m**: *(+39) 3408816643 | *e: >> *giacom...@gmail.com <mailto:giacom...@gmail.com> >> <mailto:giacomo.ro...@uniroma1.it> >> Member of Fortran-FOSS-programmers >> <https://github.com/Fortran-FOSS-Programmers>
