![]() I have tried skipping the chkstk() call in the dissasembler but in crashes the program. I have increased the reserved stack space to hundreds of Mb and the problem persists. I have worked really hard to move arguments (especially arrays) into a module, but I keep getting the same errorĬan anyone offer any suggestions on what is causing the SO, or how to debug it? ![]() I understand possible stack issues if the arguments are more than 8kb in size, but in this case we have 7 x real(64) + 11 x int(32) + 2 x 2 x char(8) = 832 bits only in passed arguments. With similar variable specifications except for crpm, qeff, rev and qqmax are arrays of which only the i-th elements is used for each SRF() call. & luin, luout, lurtpo, ludiag, ndiag, n, nzdepth, & qqmax(i), lvtyp1, lvtyp2, avespd, fridry, REAL*8 den, crpm, qeff, rev, qqmax, avespd, fridryĪnd called like this: CALL SRF(den, crpm(i), i, inose, qeff(i), rev(i), INTEGER*4 lvtyp1, lvtyp2, luin, luout, lurtpo, ludiag, ndiag, n, & luout, lurtpo, ludiag, ndiag, n, nzdepth, & qqmax, lvtyp1, lvtyp2, avespd, fridry, luin, The procedure in question is declared as (pardon the fixed file format) SUBROUTINE SRF(den, crpm, icrpm, inose, qeff, rev, ![]() The failure message comes from the dreaded _chkstk() call when an internal subroutine is called (called from the. I am compiling 32-bit on a Windows 7 64-bit system. The problem is that the execution fails on the Intel binary, but works well with Compaq. ![]() dll I can compile them with Compaq Visual Fortran 6.6C or Intel Visual Fortran 12.1.3.300 (IA-32). Using identical source files for a Fortran. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |