Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

forrtl: severe (174): SIGSEGV, segmentation fault occurred

suwei-igp
Beginner
‎04-26-2006 09:22 AM
559 Views
Hello everyone,

I am using Intel EM64T Fortran Compiler 9.0.031 on SuSE Linux10.0 (x64) with 2048 MB RAM and 2048MB swap. I defined several arrays by the style such as"PARAMETER (MAXEL=1000)"and compiled with the options "ifort -i_dynamic -mcmodel=large". When MAXEL value was smallthe programcould run and ouput results,but when MAXEL value was largerthe programshowed the following information and stopped:

forrtl: severe (174): SIGSEGV, segmentation fault occurred.

So I want to know how to solve this matter? Could Increasing physics memory solve this matter or Intel Fortran Compiler's bug?

suwei-igp

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎05-12-2006 07:37 PM
559 Views
First, you probably don't want -mcmodel large - medium should do.

Otherwise, there's no way to tell what the problem is without analyzing the application in question. Linux can be very unhelpful at identifying issues such as insufficient datasize. You might see if "ulimit datasize" helps at all. You may also want to consider making these arrays ALLOCATABLE and allocating them dynamically.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.