Memory Space Issue?

[pfwang]

I was able to compile and run a fortran code, which required a large memory space. After the compiled code started execution for some time, the code crashed. The following messages showed up on the debug screen:

Loaded 'ntdll.dll', no matching symbolic information found.
Loaded 'C:WINDOWSsystem32kernel32.dll', no matching symbolic information found.
Loaded 'C:PFWorkingSDBCH3DCH3D-SDBCH3D-SDBDebug etcdf.dll', no matching symbolic information found.
The thread 0xF64 has exited with code 0 (0x0).
The program 'C:PFWorkingSDBCH3DCH3D-SDBCH3D-SDBDebugjame_ch3d_transp_sinclair_FC_netCDF.exe' has exited with code 0

Can anyone provide any help on this? What doesthis mean? Thanks.

[pfwang]

I was supplied a code, which contains multiple .for files with some .inc (include files). I also found a UTILIO.ASM file (which may be for utility for input/output). This UTILIO.ASM looks like a source file, but does not look like fortran file. It seems to control the input/output withoperations on screens (erase screen, ... ) Do you have any idea what this file is? How do I compile it into the executable? Thanks...

[Steven_L_Intel1]

Could be assembler. Can you post an excerpt? If it is assembler, you need to get Microsoft MASM which is a free download for Visual Studio users. You'll need to be sure that the assembler routine follows the expected calling convention of the code that calls it.

[pfwang]

Thanks, yes I think it is an assembler. I have downloaded Microsoft MSAM. How do I compiles the .for files with the assembler file? My previous experience with DVF has involved only with .for and .inc files.

Thanks.

[Steven_L_Intel1]

You use MASM to create .obj files and then link those with your Fortran-compiled .obj files. Believe it or not, there is information about mixed MASM-Fortran applications in the DVF/CVF Programmer's Guide (and the IVF Building Applications manual.)

[grg99]

Hmmmm, there may be a problem. Usually when there is assembly language to clear the screen, that code was intended to run under the old MSDOS. Are there calls to "int 21h" or "int 10h" ? Those are the old obsolete ways of clearing the text screen in MSDOS. They only work if called from 16-bit ral mode code.

Those calls will NOT work with most modern compilers that generate 32 pr 64-bit protected mode code.

You may just want to write Fortran replacements for those routines, which at first just do


Print *, ""


eventually when the rest of the program is running okay you can go back and patch in the correct modern ways of clearing the screen, burping the baby, etc, etc..

[farrow22]

Steve,

for 64-bit development on 64-bit Windows, do you still recommend VS.NET 2003 over VS2005?

Thanks, Roger

[Steven_L_Intel1]

No, for 64-bit, VS2005 is really the only option as that gives you debugging and VS building for 64-bit, which VS2003 does not.