[Wien] an error occured when running AIM (SURF)

Laurence Marks L-marks at northwestern.edu
Tue Jun 19 14:42:33 CEST 2007


Unfortunately the exact location of a SIGSEGV problem does not have to
be the line where the code crashed, instead somewhere else. What is
happening is that an array somewhere is going out of bounds. By chance
it is not crashing the code with pgi but does with ifc -- such things
are common.

First, a guess: how many sampling points total are you using? There is
a hard limit NGAUSS set in param.inc which is set to 200 in my version
and I seem to remember limits you to 200. If you want more, increase
it an recompile -- this might solve the issue.

If not, add -check to the compilation (ifc) and recompile. This may
give a different (more correct) location for the error although it
might also give misinformation.

On 6/19/07, lu wei <weilu7910 at yahoo.com.cn> wrote:
> Dear all:
>    I test the AIM using TiC structure. When I use the AIM (SURF)procedure
> compiled using pgi and static lab, It works well. However, When I use the
> AIM(SURF) code compiled using ifc 9 and mkl 8, an error message appeared as
> following:
> forrtl: severe (174): SIGSEGV, segmentation fault occurred
> Image              PC        Routine            Line        Source
> aim                0807A055  Unknown               Unknown  Unknown
> aim                0807F219  Unknown               Unknown  Unknown
> aim                080610C2  Unknown               Unknown  Unknown
> aim                0804DA41  Unknown               Unknown  Unknown
> aim                0804D50E  Unknown               Unknown  Unknown
> aim                0804BA42  Unknown               Unknown  Unknown
> libc.so.6            42015574  Unknown               Unknown  Unknown
> aim                0804B971  Unknown               Unknown  Unknown
> I searched the archive, I found that L.Marks once suggested to add
> -traceback to the compilation options. I did it, the return result likes
> this:
> forrtl: severe (174): SIGSEGV, segmentation fault occurred
> Image              PC        Routine            Line        Source
> aim                08077065  dpchfe_                  2437  SplineFit.f
> aim                0807BE7C  checkcspline_             141  CheckCSpline.f
> aim                0805F8F3  integrho_                 320  integrho.f
> aim                0804D800  main1_                    166  main1.f
> aim                0804D340  MAIN__                     52  aim.f
> aim                0804BA42  Unknown               Unknown  Unknown
> libc.so.6            42015574  Unknown               Unknown  Unknown
> aim                0804B971  Unknown               Unknown  Unknown
> the line of 52 in aim.f is CALL MAIN1()
> the line of 166 in main.f is call integrho()
> the line of 320 in integrho.f is call
> CheckCspline(ErrorSum,ErrorAbs,weit)
> the line of 141 in CheckCSpline.f is call
> DPCHFE(NPH,Rphi,rsurface(1,j),DPH(1,j),1,.true.,2,PhiInt,RP,IERR)
> the line of 2437 in SplineFit.f is IERR = 0
>   So, how to solve this problem?
> Thank you very much!
>
>  ________________________________
>  雅虎免费邮箱-3.5G容量,20M附件
>
>
> _______________________________________________
> Wien mailing list
> Wien at zeus.theochem.tuwien.ac.at
> http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
>
>


-- 
Laurence Marks
Department of Materials Science and Engineering
MSE Rm 2036 Cook Hall
2220 N Campus Drive
Northwestern University
Evanston, IL 60208, USA
Tel: (847) 491-3996 Fax: (847) 491-7820
email: L-marks at northwestern dot edu
Web: www.numis.northwestern.edu
EMM2007 http://ns.crys.ras.ru/EMMM07/
Commission on Electron Diffraction of IUCR
www.numis.northwestern.edu/IUCR_CED


More information about the Wien mailing list