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.

Bus Error

scroto
Beginner
1,600 Views
Hi,

Im quite new to the intel fortran compiler, but have managed to install and configure it. It also compiles a program that i have written, but when this program is run it displays 'Bus Error' and the program exits. This program runs fine on other machines so I have the feeling there is something wrong with either my machine or the install of the compiler. Any help with this problem would be much appreciated.

I am running SuSE-Linux 10 x86_64, on an AMD Atholon 3800+ if this is any help.
0 Kudos
5 Replies
jeff_ryman
Beginner
1,600 Views
I have not received this error on linux, but a "bus error" on an older version of HP-UXwas traced to a mismatch in the number of arguments between a call and a subroutine. This was before the advent of optional arguments in Fortran.
0 Kudos
scroto
Beginner
1,600 Views
After further testing of the program I have found it also gives an error of :

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libc.so.6 00002AAAAB04A513 Unknown Unknown Unknown
libc.so.6 00002AAAAB04B1F1 Unknown Unknown Unknown
libc.so.6 00002AAAAB04CB04 Unknown Unknown Unknown
a.out 0000000000418FDB Unknown Unknown Unknown
a.out 0000000000407700 Unknown Unknown Unknown
a.out 000000000040871C Unknown Unknown Unknown
libc.so.6 00002AAAAB00F4C0 Unknown Unknown Unknown
a.out 0000000000449472 Unknown Unknown Unknown
a.out 00000000004210A9 Unknown Unknown Unknown
a.out 000000000041FF3C Unknown Unknown Unknown
a.out 000000000040536B Unknown Unknown Unknown
a.out 0000000000403C2A Unknown Unknown Unknown
libc.so.6 00002AAAAAFFD5AA Unknown Unknown Unknown
a.out 0000000000403B6A Unknown Unknown Unknown

and the program needs to be killed for it to terminate. It also only gives these errors if the arrays in the program are large eg greater than 60 elements in 1 dimension. If they are less the program works fine.
0 Kudos
TimP
Honored Contributor III
1,600 Views
Did you try compiling and running with options such as -C -traceback, to attempt to catch subscript range errors and the like?
0 Kudos
scroto
Beginner
1,600 Views
As I said in an earlier post im am pretty new to the intel compiler so i don't really know what im looking for but the error i got with the -C option is :


forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libc.so.6 00002AAAAB00F4C0 Unknown Unknown Unknown
a.out 0000000000448DF2 Unknown Unknown Unknown
a.out 000000000041B915 Unknown Unknown Unknown
a.out 000000000041A7A8 Unknown Unknown Unknown
a.out 000000000040527F Unknown Unknown Unknown
a.out 0000000000403BEA Unknown Unknown Unknown
libc.so.6 00002AAAAAFFD5AA Unknown Unknown Unknown
a.out 0000000000403B2A Unknown Unknown Unknown
*** glibc detected *** double free or corruption (out): 0x0000000000573560 ***
foretell: error (76): IOTA trap signal


and the error given with -traceback is :


foretell: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libc.so.6 00002AAAAB1124C0 Unknown Unknown Unknown
a.out 0000000000446C6E Unknown Unknown Unknown
a.out 0000000000411721 Unknown Unknown Unknown
a.out 00000000004105B4 Unknown Unknown Unknown
a.out 0000000000404E08 MAIN__ 58 genes.f90
a.out 0000000000403BEA Unknown Unknown Unknown
libc.so.6 00002AAAAB1005AA Unknown Unknown Unknown
a.out 0000000000403B2A Unknown Unknown Unknown
*** glibc detected *** double free or corruption (out): 0x0000000000570560 ***
foretell: error (76): IOTA trap signal


I had a look at line 58 in the program but it is only a WRITE(6,*)'' command. I don't know if these are at all helpfully. If there is a log the compiler makes which would be useful could you please tell me where it is located.
0 Kudos
Steven_L_Intel1
Employee
1,600 Views
At this point I suggest you contact Intel Premier Support and attach a test case that reproduces the problem.
0 Kudos
Reply