Visual Fortran常见错误内容
Visual FoxPro上机操作常见错误
3、记录的修改
记录的修改有编辑修改(EDIT)、条件修改(CHANGE)、窗口浏览修改(BROWSE)、自动替换修改(REPLACE)等多种修改方式。
Visual FoxPro上机操作常见错误
在我们上机的过程中，难免会出现各种各样的错误，遇到各种各样的错误提示，那么如何根据这些错误提示找出我们的真正的错误根源呢？在这里我为大家整理了一些常见的错误的分析和解决方法。
一、输入命令时常见错误分析
1、不能识别的命令谓词
产生原因：
（1）关键词拼写错误
（2）命令动词与短语、短语中各单词之间没有用空格隔开
其中替换清单的格式如下:
<字段名1> WITH <替换内容1>[,<字段名2> WITH <替换内容2>……]
学生使用REPLACE命令时经常出错的地方主要有二:
一是当要求对所有记录指定字段进行自动替换修改时,未能指定记录范围ALL ,结果系统只对当前记录进行自动替换修改;
二是输入<替换内容>的数据类型与对应字段的数据类型不一致。
2、创建表文件时忽略了小数点和小数位数也包含在字段宽度之内的事实。导致输入数据时产生溢出。
3、在Visual FoxPro中，A~Z单个英文字母已被专门用作工作区的别名，用户不能在用他们作为表文件名。错误提示：“别名已被使用”。
三、记录操作时常见错误分析
1、记录的显示
单纯显示表记录的命令主要有LIST和DISPLAY两个。
3、数据孤立
fortran常见错误
FAQ之常见错误2014-02-02 13:45:35 来源：Fcode研讨团队评论：2点击：4419本文从编译错误，链接错误，运行时错误，计算结果错误等四个方面介绍了常见的错误及解决思路。
适合初学者阅读。
首先应该明确：错误有哪几种？我们当前遇到的是何种错误？阐述这些问题前，我们先讨论一下常规的应用程序开发的过程：1>>编写代码，使用一个或多个源代码文件。
2>>对第一步的每一个源代码文件执行编译操作。
得到一个或若干个目标代码。
3>>将目标代码，运行时库（Run-time Library）和其他使用到的函数库链接起来。
得到一个可执行文件（EXE 或其他）4>>编写程序的说明书，必要的（输入）数据文件5>>将上述得到的结果发布给用户。
（发布的方式可以是刻录成光盘，销售，放在网站上供别人下载，或者其他）6>>用户得到程序后，运行，输入数据，得到计算结果。
对于很多 Fortran 程序员来说，可能用户就是自己，也可能仅仅是自己教研室的同事同学。
所以第4，5，6步骤很多时候不明显。
而如果使用集成开发环境（IDE）进行开发，第1，2，3步骤又可以一键完成。
因此，很多初学者就认为，写程序就是：输入代码，运行，得到结果。
这样的理解太狭义。
不管我们面对什么使用者来写代码，程序开发应该是上述的过程。
我们的编译器，编译环境，也是为这个过程而设计的。
于是，我们将错误分为四种：一. 编译错误（发生在第2步）编译错误，一般是源代码书写格式不正确，不符合语法要求。
二. 链接错误（发生在第3步）链接错误，一般是源代码结构不完整，运行时库或函数库使用不合理。
三. 运行时错误（发生在第6步）运行时错误，一般是执行代码时，遇到了事先未料及的错误。
比如内存不足了，磁盘空间不够了，输入文件格式不对了，输出文件写入失败了等等。
四. 计算结果不符合预期（程序代码不规范，或不符合你的设想）计算结果不符合预期，可能性就很多了。
Fortran 运行中给出的系统错误及解决方法
. Fortran 运行中给出的系统错误及解决方法以下均为linker tools errors and warningsLinker Tools Error LNK1000unknown error; consult documentation for technical support options Note the circumstances of the error, try to isolate the problem and create a reproducible test case, then contact technical support.Linker Tools Error LNK1101incorrect MSPDBxx.DLL version; recheck installation of this product The version of MSPDBxx.DLL available on your system does not match the version required by this tool.Linker Tools Error LNK1102out of memoryThere was not enough memory for the tool to run. Probably the paging file exceeded available disk space. If a shortage of disk space is not the cause, note the circumstances of the error, try to isolate the problem and create a reproducible test case, then request technical support.Linker Tools Error LNK1103debugging information corrupt; recompile moduleProbably the compilation was terminated before a valid object file was created.Recompile the given object file. If recompiling does not correct the problem,note the circumstances of the error, try to isolate the problem and create a reproducible test case, then consult technical support.Linker Tools Error LNK1104cannot open file "filename"The tool could not open the given file. One of the following may be a cause:l There was not enough disk space.l The file does not exist.l The filename or its path was incorrectly specified.l The specified drive is invalid.l The file does not have the appropriate permissions.l The path for filename expands to more than 260 characters.l If the given file is named LNKn, which is a filename generated by the linker for a temporary file, then the directory specified in the TMP environment variable may not exist, or more than one directory is specified for the TMP environment variable. (Only one directory path should be specified for the TMP environment variable.)l If the error occurs on the executable filename, an earlier version of the executable may still be running. You will need to terminate the executable before linking it. In Windows NT (including Windows 2000) or Windows 95,you can use the utility PVIEW to look for and kill instances of the application.l If the error message occurs for a library name, and you recently ported the .MAK file from a previous Microsoft Visual C++ developmentLinker Tools Messages Page 3 of 37environment, the library may no longer be valid. Ensure that the library still exists in this circumstance.l If the error message occurs for a library name such as CONSOLE.LIB, and you included object modules from an older Fortran developmentenvironment such as Microsoft Fortran PowerStation, recompile all source files with Visual Fortran to create new object files and libraries.Linker Tools Error LNK1105cannot close file "filename"The tool could not close the given file. Possibly there was insufficient disk space available.Linker Tools Error LNK1106invalid file or disk full: cannot seek to locationThe tool could not read or write to location in a memory-mapped file:l Your disk may be too full to complete the link. Free up some space and try the link again.l The error may be a result of trying to link over a network. Some networks do not fully support the memory-mapped files used by the linker. Try linking on your local disk to see if that fixes the problem.l There may be a bad block on your disk. Although the operating system and disk hardware should have detected such an error, you may want to run a disk checking program.Linker Tools Error LNK1107invalid or corrupt file: cannot read at locationThe tool could not read the file. Recreate the file.Linker Tools Error LNK1108cannot write file at locationThe tool could not write to the file. One of the following may be a cause:l There was not enough disk space to create the file.l The drive being written to was not available, possibly due to a network problem.Linker Tools Error LNK1109cannot remove file "filename"LIB could not delete the given file. Before LIB writes the new version of a library, it removes the existing library file. One of the following may be a cause:l The given file does not have the appropriate permissions.l The drive containing the file was not available, possibly due to a network problem.Linker Tools Error LNK1110Linker Tools Messages Page 4 of 37cannot rename file "filename"LIB could not rename the given file. When LIB builds a new version of a library, it creates atemporary file, then renames the file. One of the following may be a cause:l The given file does not have the appropriate permissions.l The drive containing the file was not available, possibly due to a network problem.Linker Tools Error LNK1111invalid /BASE argument "argument"The /BASE option was incorrectly specified. Either no argument was specified or argument is not a number.Linker Tools Error LNK1112module machine type "type1" conflicts with target machine type "type2"The object files specified as input were compiled for different machine types.Linker Tools Error LNK1113invalid machine typeThe machine type specified in the object header is not valid. Probably the file is corrupt. Rebuild the object. See Corrupt Object File for more information.Linker Tools Error LNK1115/MACHINE option requiredLINK or LIB cannot determine the machine type for objects that are provided entirely from libraries. Either specify the /MACHINE option with the appropriate machine type or specify at least one object file in the input.Linker Tools Error LNK1117syntax error in option "option"The given option was not correctly specified.Linker Tools Error LNK1118syntax error in keyword statementThe given module-definition statement was not correctly specified.Linker Tools Error LNK1119invalid ordinal number "argument"The argument following the at sign (@) in an ordinal specification was not avalid number. An ordinal number is an optional argument in either an /EXPORToption in a LINK or LIB command or an EXPORTS statement in a moduledefinitionfile. It is an index into the exports table. The number must be aninteger in the range 1-65535.Linker Tools Error LNK1120number unresolved externalsLinker Tools Messages Page 5 of 37Error LNK1120 gives you a count (number) of unresolved externals for this link.The conditions that cause unresolved externals are described with errorLNK2001 (see Linker Errors LNK2001 to LNK2014), which precedes this error message (once for each unresolved external).Linker Tools Error LNK1121duplicate ordinal number "number"The given ordinal number was specified more than once in either an /EXPORT option in a LINK or LIB command or an EXPORTS statement in a moduledefinition file. Ordinal numbers must be unique integers in the range 1-65535.Linker Tools Error LNK1123failure during conversion to COFF: file invalid or corruptThe object or resource could not be converted to COFF. This tool requires the format of all input files to be COFF. If an input file is not COFF, the tool runs a conversion tool, either CVTOMF (to convert 32-bit OMF objects) or CVTRES (to convert resource files). This error is preceded by errors or warnings from the conversion tool. One of the following may be a cause:l The file is corrupt.l The file is not a valid file type. An example of an invalid type is a 16-bit OMF object.Linker Tools Error LNK1127library is corruptThe library file is corrupt. Rebuild the library.Linker Tools Error LNK1129cannot find resolution for weak extern symbolThe given weak external symbol does not have a default resolution. Probablythe symbol table is corrupt. Rebuild the object file. See Corrupt Object File for more information.Linker Tools Error LNK1130Linker miscalc (base relocations off by number)There was not enough space in the image to write base relocations.Linker Tools Error LNK1131no library file specifiedThe LIB /EXTRACT command required a library as input, but a library filenamewas not specified.Linker Tools Error LNK1132invalid format for MS-DOS stub file "filename"The filename specified with the /STUB option was not a valid real-mode MS-DOS executable (.EXE) file.Linker Tools Messages Page 6 of 37Linker Tools Error LNK1136invalid or corrupt fileThe input file either has a corrupt header or is zero size or abnormally small.See Corrupt Object File for more information.Linker Tools Error LNK1137invalid argument specified with /SECTIONEither the name or the attributes argument to the /SECTION option is specified incorrectly.Linker Tools Error LNK1140too many modules for program database; relink with /PDB:NONEThe project contains more than 4096 modules. One of the following is asolution:l Relink using /PDB:NONE.l Compile some modules without debugging information.l Reduce the number of modules.Linker Tools Error LNK1141failure during build of exports fileLINK could not build the exports (.EXP) file. Causes of this error include system problems such as insufficient memory and syntax errors in options or moduledefinition statements. This error is preceded by another error that givesadditional information.Linker Tools Error LNK1143invalid or corrupt file: no symbol for COMDAT section numberThe object file is corrupt. Rebuild the file. See Corrupt Object File for more information.Linker Tools Error LNK1144error with LINK_REPRO var; cannot open "filename"The linker could not create filename. One of the following may be a cause:l Check that you've set your LINK_REPRO environment variable to anexisting directory and not the current directory.l Make sure there are no read-only files in the directory.l Make sure none of the files in the LINK_REPRO directory are open byanother process, because the linker needs to write to them.Linker Tools Error LNK1145/MERGE created circular link for section "section"You attempted to merge a section into itself. Check the /MERGE options.Linker Tools Error LNK1146Linker Tools Messages Page 7 of 37no argument specified with option "option"The given option requires an argument.Linker Tools Error LNK1147invalid number specified with option "option"The argument to the given option was specified incorrectly.Linker Tools Error LNK1148failure during conversion to COFF: cannot copy temp file filenameEDITBIN could not convert the input file to COFF. When EDITBIN converts a file,it creates a temporary file, then copies the file. One of the following may be a cause: l The given file does not have the appropriate permissions.l There was not enough disk space to create the file.l The drive being written to was not available, possibly due to a network problem.Linker Tools Error LNK1149output filename matches input filename "filename"The output filename specified with the /OUT or /IMPLIB option was the same asan input file.Return to Main Linker Error PageLinker Errors LNK1152 to LNK1189Linker Tools Error LNK1152cannot resolve one or more undecorated symbolsThis error is preceded by one warning LNK4022 for each undecorated symbolthat could not be resolved and by at least two warnings LNK4006 for the duplicate symbols found for the undecorated symbol.Linker Tools Error LNK1153/VXD command-line option requiredYou attempted to build a virtual device driver without the /VXD option. Relinkwith the /VXD option.Linker Tools Error LNK1154specified import library filename matches exports file "filename"The filename specified with LINK /IMPORT or with LIB /DEF /OUT conflicted with the filename given by LINK or LIB to the exports file, which is formed from the base name of the main output file and the extension .EXP.Linker Tools Error LNK1155special symbol "symbol" already definedLinker Tools Messages Page 8 of 37The given symbol is reserved for use by LINK.Linker Tools Error LNK1156.sbss section not supportedAn object file contained an .sbss section.Linker Tools Error LNK1157fixup overflow; offset of target symbol "symbol" greater than +-8MBThe VXD is too large, or the sections are not arranged properly.Linker Tools Error LNK1158cannot run "filename"The given executable file called by LINK is not in the directory that contains LINK and is not in a directory specified in the PATH environment variable. Linker Tools Error LNK1159no output file specifiedNo name was specified for the main output file (executable file or DLL). LINK derives the default name of the output file from the base name of the first object file. If no object files are specified, and if the /OUT option is not used, this error occurs.Linker Tools Error LNK1160library with zero objects not allowedAn attempt was made to remove an object from a library that contained only that object. The object was not removed.Linker Tools Error LNK1161invalid export specificationEither the /EXPORT option or the EXPORTS module-definition statement incorrectly specified an export. A possible cause is a typing error.Linker Tools Error LNK1162expected aux symbol for comdat section numberThe linker expected to find an auxiliary symbol table for the indicated COMDAT but could not. The object file is probably corrupt. See Corrupt Object File for more information.Linker Tools Error LNK1163invalid selection for comdat section numberThe byte in the object file indicating the type of COMDAT section is invalid. The object file is probably corrupt. See Corrupt Object File for more information. Linker Tools Error LNK1164section section alignment (number) greater than /ALIGN valueThe alignment size for the given section in the object file exceeds the value specified with the /ALIGN option. The /ALIGN value must be a power of 2 and Linker Tools Messages Page 9 of 37must equal or exceed the section alignment given in the object file. Either recompile with a smaller section alignment or increase the /ALIGN value. Linker Tools Error LNK1165link failed because of fixup errorsThe build failed due to fixup errors. The /FORCE or /FORCE:UNRESOLVED option overrides this error.Linker Tools Error LNK1166cannot adjust code at offset=offset, va=valueLINK was unable to pad the code as required. Certain instructions are not allowed to cross page boundaries on some processors. LINK attempts to add pads to correct this situation. In this case, LINK could not work around the problem.Linker Tools Error LNK1167file contains relocs but header has no machine typeA converted COFF object did not have a machine type specified in its header. One cause of this error is omitting a machine type when converting a .RES file in a separate step before linking.Linker Tools Error LNK1168cannot open filename for writingThe given file does not have write permission.Linker Tools Error LNK1169one or more multiply defined symbols foundThe build failed due to multiple definitions of one or more symbols. This error is preceded by error LNK2005. The /FORCE or /FORCE:MULTIPLE option overrides this error.Linker Tools Error LNK1170line in command file contains limit or more charactersThe length of a line in a command file must be less than the given limit.Linker Tools Error LNK1171unable to load filenameThe given DLL was unavailable. The possible locations for the DLL are the current directory, the system directory, the Windows directory, and the directories specified in the PATH environment variable.Linker Tools Error LNK1172more than one object with the name "object" found; rename object(s) or relink /PDB:NONEA library contained two or more objects with the same name. Do one of the following:Linker Tools Messages Page 10 of 37l Rename the objects using unique names and rebuild the library.l Link using the /PDB:NONE option.Linker Tools Error LNK1173unable to find entrypoint function in filenameThe given function does not exist in the given DLL.Linker Tools Error LNK1174unable to /REBASE filename; not a valid Win32 imageThe format of the given file was invalid.Linker Tools Error LNK1175failed to /REBASE filenameThe rebase operation failed on the given file.Linker Tools Error LNK1177TOC size limit exceededThe linker was unable to create a TOC (Table of Contents) in your image file. The limit is 2048 entries in the TOC.Linker Tools Error LNK1178missing MODEND record; file is invalid or corruptThe linker tool tried to convert an OMF object module to COFF format but could not find an expected MODEND (module end) record in the OMF object. The OMF object module is corrupt and needs to be recreated or recopied. See Corrupt Object File for more information.Linker Tools Error LNK1179invalid or corrupt file: duplicate comdat comdatAn object module contained two or more COMDATs with the same name. One possible cause is if you use the Visual C++ /H option with the Visual C++ /Gy option. The /H option limits the length of external names, and the /Gy option packages functions in COMDATs.Linker Tools Error LNK1180insufficient disk space to complete linkThe linker tool was unable to complete a file operation since the operating system reported that the disk is full. Free up space on your local and network drives (if you are writing files there).Linker Tools Error LNK1181cannot open input file "filename"The linker tool could not find "filename" because it does not exist or the path was not found.Linker Tools Error LNK1182Linker Tools Messages Page 11 of 37cannot have more than 64K exportsYou have reached the linker's limit of 65,536 exports.Linker Tools Error LNK1183invalid or corrupt file: extended relocation count number less than 65535The COFF object file is corrupt since it contains an extended relocation count that is less than 0xFFFF. See Corrupt Object File for more information.Linker Tools Error LNK1184invalid section name "section" specified in option or directive "option"You gave the linker an invalid section name in option. Invalid section names contain "$" or blanks.Linker Tools Error LNK1185invalid section name "section" specifiedYou gave the linker an invalid section name in a .DEF file. Invalid section names contain "$" or blanks.Linker Tools Error LNK1186invalid or corrupt COFF object; reloc to undefined static symbol "symbol"Your COFF object module is corrupt since it contains a relocation entry for an undefined static symbol. See Corrupt Object File for more information.Linker Tools Error LNK1187Corrupt object - unmatched name relocation; ignoredYour object file contains bad relocation information. Recopy or recreate the object file. See Corrupt Object File for more information.Linker Tools Error LNK1188BADFIXUPSECTION:: invalid fixup target "symbol"; possible zero length section This message is issued only for VxD links when the target of a relocation does not have a section. With LINK386 (an older version), an OMF GROUP record (generated by a MASM GROUP directive) may have been used to combine the zero length section with another non-zero length section. COFF format does not support the GROUP directive and zero-length sections. When LINK automatically converts this type of OMF objects to COFF, this error may occur.Linker Tools Error LNK1189LIBTOOMANYMEMBERS:: library limit of number objects exceededThe limit of 65535 objects or members in a library has been exceeded.Return to Main Linker Error PageLinker Errors LNK1190 to LNK1581Linker Tools Error LNK1190Linker Tools Messages Page 12 of 37invalid fixup found, type typeThe object file has become corrupted. Recompile.Linker Tools Error LNK1194cannot delay-load dll name due to import of data symbol symbol name; relink without /DELAYLOAD:dll nameYou cannot delay load a DLL if data is imported from it.Linker Tools Error LNK1195target machine "machine" requires "option"Add the required option.Linker Tools Error LNK1196invalid or corrupt import object: unknown versionThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1197invalid or corrupt import object: unknown typeThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1198invalid or corrupt import object: unknown name typeThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1199invalid or corrupt import object: non-zero reserved fieldsThe import library has become corrupted. Rebuild the library.Linker Tools Error LNK1200error reading program database "filename"The given program database (PDB) could not be read, probably because it is corrupted. If filename is the PDB for an object file, recompile the object file; use the /debug:full and /pdbfile options. If filename is the PDB for the main outputfile and this error occurred during an incremental link, delete the PDB and relink.Linker Tools Error LNK1201error writing to program database "filename"; check for insufficient disk space LINK could not write to the program database (PDB) for the output file. One of the following may be a cause:l The file is corrupted. Delete filename and relink.l There was not enough disk space to write to the file.l The drive being written to was not available, possibly due to a network problem.Linker Tools Error LNK1202Linker Tools Messages Page 13 of 37"filename" missing debugging information for referencing moduleThe given program database (PDB) for an object file was invalid. Recompile the object file; use CL's /Zi option.Linker Tools Error LNK1203"filename" missing current debugging information for referencing module The given program database (PDB) for an object file was invalid. Recompile the object file; use CL's /Zi option.Linker Tools Error LNK1204"filename" compiled /Yc /Yu /Z7; cannot create PDB; recompile with /Zi Multilayered program databases (PDBs) are not supported in combination with old-style debugging information. Recompile using CL's /Zi option.Linker Tools Error LNK1206cannot overwrite Visual C++ 1.0 PDB "filename"; delete and rebuildThis version of LINK cannot write to an existing program database (PDB) created using older versions of the visual development environment. Delete filename and rebuild.Linker Tools Error LNK1207incompatible PDB format in "filename"; delete and rebuildThis version of LINK cannot write to the existing program database (PDB). Delete filename and rebuild.Linker Tools Error LNK1209program database "filename" differs from previous link; relink or rebuildThe given program database (PDB) is invalid and possibly corrupt. Relink. If filename is also the PDB for an object file, recompile to recreate the PDB. Linker Tools Error LNK1210insufficient memory for incremental link; relink with /INCREMENTAL:NO There was not enough virtual memory available for LINK to create the incremental status (.ILK) file.Linker Tools Error LNK1211precompiled type information not found; "filename" not linked or overwritten The given object file, compiled with /Yc, either was not specified in the LINK command or was overwritten.Linker Tools Error LNK1212error opening program database; file is in useThe PDB is already in use by another application.Linker Tools Error LNK1213unexpected import object encounteredThe import library has become corrupted. Rebuild the library.Linker Tools Messages Page 14 of 37Linker Tools Error LNK1221a subsystem can't be inferred and must be definedThe linker does not have enough information to infer which subsystem you will target your application. To fix this error, use the /SUBSYSTEM option.Linker Tools Error LNK1561entry point must be definedThe symbol specified by the /ENTRY option is not defined.Linker Tools Error LNK1581corrupted object or old compiler (bad Pcode entry point)Your object file contained a bad entry point. The object file is probably corrupt.。
fortran90常见错误
1、运行fortran时出现forrt1:severe<59>:list-directed I/O syntax error,unit 1,file G:\1\1\meat.dat怎么办这是通道1 ，链接到文件meat.dat 的读写出错了。
这问题你得认真检查类似read( 1 , * ) 或write( 1 , * ) 这样的语句，错误原因挺多的。
比如二进制文件用了文本方式读取，比如变量列表与文件不匹配。
问：另外forrt1:severe<161>:program exception -array bounds exceeded是怎么回事？回答：数组越界，也是很常见的错误。
比如real a(100)如果你使用了a(101) 就会越界，因为a 数组只有100 个元素。
2、fortran运行提示error M6201：math-**，现将代码贴出，求高手帮忙看看，急求解答！我不能确定你的错误是怎么引起的。
可能咱们的编译器不同。
你的代码在我这里的问题是：虚参和实参精度不同。
在程序中，你定义了部分real*8，但是对应的虚参和返回值却定义为real。
比如主程序里的z1（双精度），传入函数g里面的x却定义为单精度。
主程序Do 死循环了。
z2_jiashe 和 z2_suan 每一次循环都没有发生改变，于是永远跳不出循环。
我给你的建议是：同一个程序，统一使用real*8 或real*4，尽量不要混用，除非你很自信能理清他们的关系。
检查Do 循环，尤其是z2_jiashe 和z2_suan，是否应该每次循环不同？fortran_排除错误(2012-04-20 23:22:44)安装好VISUAL FORTRAN后1、运行Developer studio即可开始编译FORTRAN程序2、选择File菜单中的New选项3、在弹出的对话框选择projects标签，其他标签不用管，projects格式选用Fortran console application；在project name里命名（最好英文名），点击“ok ”4、接下来画面中，选择“an empty project”，点击“finish”5、接下来画面点击“ok”6、再选择一次File菜单中的new7、对话框选用files标签，选择Fortran free format source file ，并在file里命名8、点击“ok”数Source Files 放源文件(.c、.cpp)程序的实现代码全放在这里Header Files 放头文件(.h)声明放在这里Resource Files 资源文件(.rc)放图标、图片、菜单、文字之类的，主要用来做界面的东东一般都放这里External Dependencies 除上三种以外的，程序编译时用到的文件全放这里fortran内部函数出错信息解释内部函数出错信息解释[sourcefile(line)]run-time error M62××MATH错误号函数级数学错误信息M6201 functionnames:DOMAIN error函数的自变量超出了约定的取值域，例如sqrt(-1)M6202 functionname:SING error无意义的变量。
fortran常见错误及其原因
常见fortran错误1.Incrementally linked image--PC correlation disabled.！编译终止2. forrtl:severe(157):Program Exception - access violationbounds and /warn:argument_checking options set, to see if theproblem is an out-of-bounds memory reference or a argument mismatch that causes data to be treated as anaddress.Other causes of this error include:severe(64):input conversion error, unit 2, file D:\FORTRAN2\testi！文件testi正在读写，直到读写到2时错误。
举例：程序想读写整数，却碰到变量故终止。
4 error LNKZOOI :unresolved external symbol _ SN @ 4 fatal error LNKllZO :1 unresolved externals!出现了未指定的外部函数符号Sn。
这是因为在函数子程序中错把函数名Sn写成了ns。
根据错误信息中的提示，用户在编辑窗口寻找有错位置进行修改。
连接错误往往出现在有函数调用或子程序调用的程序中，常见的错误性质有：未定的函数符号、找不到主程序或子程序、实参与虚参的个数不一致等。
注意：连接错误只给出错误代号和错误性质，不给出具体语句的行号。
5 :: error FOR229O :implicit type for 1 detected between 1 and = C :\ abc．: error FOR33Og :undefined label 10编译系统提示用户：在程序的第5行，变量i未经类型说明；在程序的第H行，标号10未定义。
Visual FoxPro上机操作常见错误分析
Visual FoxPro上机操作常见错误分析Visual FoxPro是目前微机上基于Windows平台的运行较为普遍的关系数据库管理系统。
在教学过程中我们发现,很多同学在初学Visual FoxPro时由于对Visual FoxPro的语法规则和命令涵没有准确地把握和比较深入的理解,在上机操作练习或上机操作考试时常犯一些不该犯的错误。
下面就学生在上机操作中常犯的一些典型错误进行分析,希望能对Visual FoxPro的初学者有所裨益。
一、输入命令时常见错误分析在Visual FoxPro中,对数据的操作既可使用菜单方式也可使用命令方式,这两种操作方式各有优点。
菜单方式具有直观、简单方便的特点,不需要记命令及其格式，但有时这种操作方式比较费时,效率不高;命令方式具有快捷的特点,使用它有助于初学者理解、掌握Visual FoxPro整个命令系统,在深入学习中都必须要求掌握各种命令及其作用。
因此，在教学上机安排及教学计划，都要求学生主要通过命令方式来进行。
Visual FoxPro命令的一般格式为：<命令动词>[FORM <辅助文件名>][TO <目标文件名>][<记录围>][FOR┃WHILE <条件>][FIELDS <字段名表>][OFF]其中：[ ]表示可选项, < >表示必选项, ┃表示"或者"之意。
Visual FoxPro命令通常由两部分组成，前一部分是命令动词,表示应执行的操作,后一部分是若干短语,对操作提供某些限制性说明。
Visual FoxPro规定：命令中的命令动词排在前面,各短语可以按任意次序跟在命令动词之后;命令动词与短语、短语与短语、短语中各单词间用一个或多个空格隔开;不允许在一行输入多条命令;可将一条命令分多行输入,但中途换行时应先输入一个分号再换行;命令中的命令动词、短语中的英文单词、运算符号、标点符号等应在半角状态下输入,即它们所用到的字符必须是ASCII码半角字符。
fortran常见错误及其原因
常见fortran错误1. Incrementally linked image--PC correlation disabled.！编译终止2. forrtl: severe (157): Program Exception - access violation！The program tried to read from or write to a virtual address for which it does not have the appropriate access. Try recompiling with the /check:bounds and /warn:argument_checking options set, to see if the problem is an out-of-bounds memory reference or a argument mismatch that causes data to be treated as an address.Other causes of this error include:Mismatches in C vs. STDCALL calling mechanisms, causing the stack to become corrupted References to unallocated pointers Attempting to access a protected (for example, read-only) address3 "forrtl: severe (64): input conversion error, unit 2, file D:\FORTRAN2\testi！文件testi正在读写，直到读写到2时错误。
举例：程序想读写整数，却碰到变量故终止。
4 error LNKZOOI : unresolved external symbol _ SN @ 4 fatal error LNKllZO : 1 unresolved externals! 出现了未指定的外部函数符号Sn 。
fortran常见错误及其原因
常见fortran错误1. Incrementally linked image--PC correlation disabled.！编译终止2. forrtl: severe (157): Program Exception - access violation！The program tried to read from or write to a virtual address for which it does not have the appropriate access. Try recompiling with the /check:bounds and /warn:argument_checking options set, to see if the problem is an out-of-bounds memory reference or a argument mismatch that causes data to be treated as an address.Other causes of this error include:Mismatches in C vs. STDCALL calling mechanisms, causing the stack to become corrupted References to unallocated pointers Attempting to access a protected (for example, read-only) address3 "forrtl: severe (64): input conversion error, unit 2, file D:\FORTRAN2\testi！文件testi正在读写，直到读写到2时错误。
举例：程序想读写整数，却碰到变量故终止。
4 error LNKZOOI : unresolved external symbol _ SN @ 4 fatal error LNKllZO : 1 unresolved externals! 出现了未指定的外部函数符号Sn 。
fortran常见错误及其原因
常见fortran错误1. Incrementally linked image--PC correlation disabled.！编译终止2. forrtl: severe (157): Program Exception - access violation！The program tried to read from or write to a virtual address for which it does not have the appropriate access. Try recompiling with the /check:bounds and /warn:argument_checking options set, to see if the problem is an out-of-bounds memory reference or a argument mismatch that causes data to be treated as an address.Other causes of this error include:Mismatches in C vs. STDCALL calling mechanisms, causing the stack to become corrupted References to unallocated pointers Attempting to access a protected (for example, read-only) address3 "forrtl: severe (64): input conversion error, unit 2, file D:\FORTRAN2\testi！文件testi正在读写，直到读写到2时错误。
举例：程序想读写整数，却碰到变量故终止。
4 error LNKZOOI : unresolved external symbol _ SN @ 4 fatal error LNKllZO : 1 unresolved externals! 出现了未指定的外部函数符号Sn 。
fortran90常见错误
1、运行fortran时出现forrt1:severe<59>:list-directed I/O syntax error,unit 1,file G:\1\1\meat.dat怎么办这是通道1 ，链接到文件meat.dat 的读写出错了。
这问题你得认真检查类似read( 1 , * ) 或write( 1 , * ) 这样的语句，错误原因挺多的。
比如二进制文件用了文本方式读取，比如变量列表与文件不匹配。
问：另外forrt1:severe<161>:program exception -array bounds exceeded是怎么回事？回答：数组越界，也是很常见的错误。
比如real a(100)如果你使用了a(101) 就会越界，因为a 数组只有100 个元素。
2、fortran运行提示error M6201：math-**，现将代码贴出，求高手帮忙看看，急求解答！我不能确定你的错误是怎么引起的。
可能咱们的编译器不同。
你的代码在我这里的问题是：虚参和实参精度不同。
在程序中，你定义了部分real*8，但是对应的虚参和返回值却定义为real。
比如主程序里的z1（双精度），传入函数g里面的x却定义为单精度。
主程序Do 死循环了。
z2_jiashe和z2_suan每一次循环都没有发生改变，于是永远跳不出循环。
我给你的建议是：同一个程序，统一使用real*8 或real*4，尽量不要混用，除非你很自信能理清他们的关系。
检查Do 循环，尤其是z2_jiashe 和z2_suan，是否应该每次循环不同？fortran_排除错误(2012-04-20 23:22:44)安装好VISUAL FORTRAN后1、运行Developer studio即可开始编译FORTRAN程序2、选择File菜单中的New选项3、在弹出的对话框选择projects标签，其他标签不用管，projects格式选用Fortran console application；在project name里命名（最好英文名），点击“ok ”4、接下来画面中，选择“an empty project”，点击“finish”5、接下来画面点击“ok”6、再选择一次File菜单中的new7、对话框选用files标签，选择Fortran free format source file ，并在file里命名8、点击“ok”数Source Files 放源文件(.c、.cpp)程序的实现代码全放在这里Header Files 放头文件(.h)声明放在这里Resource Files 资源文件(.rc)放图标、图片、菜单、文字之类的，主要用来做界面的东东一般都放这里External Dependencies 除上三种以外的，程序编译时用到的文件全放这里fortran内部函数出错信息解释内部函数出错信息解释[sourcefile(line)]run-time error M62××MATH错误号函数级数学错误信息M6201 functionnames:DOMAIN error函数的自变量超出了约定的取值域，例如sqrt(-1)M6202 functionname:SING error无意义的变量。
VisualFoxPro上机操作常见错误
VisualFoxPro上机操作常见错误Visual FoxPro上机操作常见错误在我们上机的过程中，难免会出现各种各样的错误，遇到各种各样的错误提示，那么如何根据这些错误提示找出我们的真正的错误根源呢？在这里我为大家整理了一些常见的错误的分析和解决方法。
一、输入命令时常见错误分析1、不能识别的命令谓词产生原因：（1）关键词拼写错误（2）命令动词与短语、短语中各单词之间没有用空格隔开（3）命令动词、短语中的英文单词、运算符号和标点符号等在全角状态下输入（4）在一行内输入多条命令（5）将一条命令多行输入时中途换行没有分号“；”2、找不到变量产生原因：（1）命令动词与短语、短语中各单词之间没有用空格隔开（2）命令动词、短语中的英文单词在全角状态下输入3、语法错误/命令中缺少必要的字句产生原因：（1）语句的结构不完整（2）运算符和标点符号是在全角状态下输入或为中文符号4、嵌套错误产生原因：（1）关键词缺少配对，如有if却没有end if，有for却没有end for（2）配对关键词的个数不相等5、操作符/操作数类型不匹配产生原因：运算符两边的变量或数据类型不一致6、缺少函数参数的值、类型或数目无效产生原因：函数参数的个数不对或传递的参数类型不对7、某某文件不存在产生原因：（1）没有设置默认路径（2）要打开的表文件或菜单文件没有存放在默认目录下（3）调用没有定义的函数或过程二、创建表文件时常见错误分析1、没有设置默认路径不少考生在事先没有用SET DEFAULT TO命令设置好当前盘当前目录的情况下进行考试,结果所创建的文件未能按要求存入指定盘指定目录中，由此常常导致上机操作考试失败。
2、创建表文件时忽略了小数点和小数位数也包含在字段宽度之内的事实。
导致输入数据时产生溢出。
3、在V isual FoxPro 中，A~Z单个英文字母已被专门用作工作区的别名，用户不能在用他们作为表文件名。
错误提示：“别名已被使用”。
visual fortran常见运行错误
Insufficient virtual memory 虚拟内存不足Integer overflow 整数溢出错误Integer divide by zero 整数除0错误Floating overflow 浮点数溢出错误Floating divide by zero 浮点数除0错误Floating underflow 浮点数下溢错误Floating point exception 浮点数异常错误Subscript out of range 数组定义超出边界Floating-point conversion failed 浮点数格式转换失败Null pointer error 空指针错误Stack overflow 堆栈溢出String length error 字符串长度超出允许范围Substring error 数组下标超出允许范围Range error 整数值超出允许范围Allocatable array is already allocated 数组重复定义Program Exception - array bounds exceeded 引用数组下标超出允许范围Program Exception - denormal floating-point operand 非法浮点数操作符Program Exception - floating stack check 浮点数堆栈检查Program Exception - integer divide by zero 整数除0错误Program Exception - integer overflow 整数溢出Program Exception - privileged instruction 非法执行特权指令Program Exception - illegal instruction 非法指令Program Exception - stack overflow 堆栈溢出Array or substring subscript expression out of range 数组下标低下数组定义下界或高于数组定义上界CHARACTER substring expression out of range 字符串非法表示Label not found in assigned GOTO list 不属于GOTO语句引用的标号INTEGER arithmetic overflow 整数运算结果出现溢出INTEGER overflow on input 输入的整数值超出允许范围Invalid INTEGER 非法整数值REAL indefinite (uninitialized or previous error) 产生非法实数Invalid REAL 非法实数REAL math overflow 实数值溢出No matching CASE found for SELECT CASE select case语句中缺少case项INTEGER assignment overflow 整数定义超出允许范围A edit descriptor expected for CHARACTER 字符型数据的格式化输入和输出需要A编辑符E, F, D, or G edit descriptor expected for REAL 实数型数据的格式化输入和输出需要E,F,D,G编辑符I edit descriptor expected for INTEGER 整数型数据的格式化输入和输出需要I编辑符L edit descriptor expected for LOGICAL 逻辑型数据的格式化输入和输出需要L编辑符Multiple radix specifiers 输入或输出语句重复说明Array already allocated 数组已分配Array size zero or negative 数组大小为0或负数Array not allocated 没有被分配的数组Invalid argument 非法参数Invalid number in input 输入非法数字Invalid string in input 输入非法字符串Comma missing in COMPLEX input 输入的多个表达式之间缺少逗号T or F expected in LOGICAL read 输入的逻辑值必须是T或FIllegal character in hexadecimal input 输入非法的十六进制数Integer expected in format 格式语句中要求的整数Initial left parenthesis expected in format 格式语句中多余的左括号Positive integer expected in format 格式语句中要求用正整数Integer expected preceding H, X, or P edit descriptor 在H、X、P编辑符前要求用整数'.' expected in format 在D、E、F、G编辑符中w和d域之间用'.'分隔Unexpected end of format 格式语句没有结束Unexpected character in format 格式语句中的非法字符M field exceeds W field in I edit descriptor 在I编辑符中M域的值大于W域的值Integer out of range in format 格式语句中的整数值超出允许范围Separator expected in format 格式语句中需要分隔符Out of range: substring starting position 'pos' is less than 1 子字符串的起始位置小于1Out of range: substring ending position 'pos' is greater than string length 'len' 子字符串的终止位置大于字符串长度Out of memory 内存不足Cannot allocate temporary array -- out of memory 由于内存不足不能分配临时数组Cannot ALLOCATE allocatable array -- out of memory 由于内存不足不能分配数组DEALLOCATE failure: ALLOCATABLE array is not ALLOCATED 释放没有被分配的数组。
fortran常见错误代码
FOR$IOS_INVREFVAR. One of the following conditions occurred:
The variable was not a member of the namelist group.
An attempt was made to subscript a scalar variable.
20
severe (20): REWIND error
FOR$IOS_REWERR. One of the following conditions occurred:
The file was not a sequential file.
The file was not opened for sequential or append access.
22
severe (22): Input record too long
FOR$IOS_INPRECTOO. A record was read that exceeded the explicit or default record length specified when the file was opened. To read the file, use an OPEN statement with a RECL= value (record length) of the appropriate size.
Fortran编译器常见错误提示及原因
附录：常见错误提示及原因安装1．关于Fortran编译器的安装和配置？在安装FEPG之前一般要先安装好Powerstation Fortran 4.0编译器，并设置好Fortran编译器的path、lib和include路径。
如果你的Powerstation Fortran 4.0编译器安装在目录C:\MSDEV下，设置如下：·在WIN 2000/XP下的设置:a.鼠标移到我的电脑图标，单击右键，然后点击属性；b.点击高级属性；c.点击环境变量，进行系统变量设置；系统变量如下图：d. 如果图上的include、lib、path几个变量没有，请点击新建；如有，点击编辑；按下面变量值进行修改：变量：path值：c:\MSDEV\bin; %path%变量：lib 值：c:\MSDEV\lib;%lib%变量：include值：c:\MSDEV\include;%include%注意：如果path、lib和include变量中有相应新增加的内容，可不增加。
如果编译器装在其它目录，则把C:\MSDEV换为该目录名。
实际上，在安装Powerstation Fortran 4.0时，会出现一个对话框，询问是否增加环境变量，如果选是，这些变量就已经配置好了。
安装fepg，需要用户有管理员权限。
2．运行FEPG命令生成Fortran源程序时，出现fl32不是内部命令也不是外部命令的错误(或fl32 is not internal command)？没配置好Fortran编译器的path路径。
按照上面第1个问题中的解答配置好path路径。
3. 运行FEPG命令生成Fortran源程序时，有些fortran源程序没连接成可执行程序，出现不能发现fepg.lib库文件的错误？安装FEPG之前，没安装和配置好Fortran编译器所致。
在安装FEPG之后出现此情况，可先按照上面第1个问题中的解答配置好Fortran编译器，然后在dos窗口下，运行FEPG所在目录下nfe.r8目录下的gfepglib.bat程序，即可生成fepg.lib库文件。
常见的fortran错误
常见的fortran错误1. Incrementally linked image--PC correlation disabled.！编译终止2. forrtl: severe (157): Program Exception - access violation！The program tried to read from or write to a virtual address for which it does not have the appropriate access. Try recompiling with the /check:bounds and /warn:argument_checking options set, to see if the problem is an out-of-bounds memory reference or a argument mismatch that causes data to be treated as an address.Other causes of this error include:Mismatches in C vs. STDCALL calling mechanisms, causing the stack to become corruptedReferences to unallocated pointers Attempting to access a protected (for example, read-only) address3 "forrtl: severe (64): input conversion error, unit 2, file D:\FORTRAN2\testi！文件testi正在读写，直到读写到2时错误。
举例：程序想读写整数，却碰到变量故终止。
4 error LNKZOOI : unresolved external symbol _ SN @ 4 fatal error LNKllZO : 1 unresolved externals! 出现了未指定的外部函数符号 Sn 。
microsoft_visual_foxpro错误总结以及知识要点概括
真、 只想 贪玩 的学 生启 发 引 导 不 够 ； 的 学 生 上完 实 验 课 有 后， 还不 知道 到底是 作 的什 么 实 验 ， 以学 生 的技 能 训 练 所
利用 考核 这个 “ 宝 ” 学生 学 习 的积 极 性 调动 起来 法 把
求， 提高学生的动手能力 ， 我们在《 动物微生物学》 教学过
程 中适 当缩 短 了理 论 教 学 时 数 ， 加 了实 验 教 学 的学 时 增 数 ， 实验 教学 与理 论 教 学 的学 时 数 比例 为 １ １使 理论 使 ：， 知识 教学 和实 践性 教学 有机结 合 、 头并 进 ， 相促 进 。 齐 互 ２２ 适 当调 整实 验课原 来 的顺序 教 材 中传 统 的实 验课 ．
贯 紧密 ， 系统性 强 ， 有利 于学 生牢 固学 习和掌握 这 门课程 。 ２ ３ 实验 实 习中加 强技能 考核 ． 实验 室是 培养 学 生实 践 能 力 的重要 场所 ， 在课 堂上无 论怎 样强 调实验 课 的 重要 但 性 ， 有少 数学 生采取 应付 态度 。对此 ， 仍 我们 改变 做 法 ， 狠 抓技 能考 核关 。专 门抽 出时 间 对学 生 进 行 面 对 面 的技 能 考 核 ， 技 能训 练与 检查 验 收 融 为 一体 ， 是 考核 不 合 格 将 凡 者 ， 绩如 实通 报家 长 ， 将成 而且 不能参 加毕 业 考试 。这 样 ， 学生 感到 有压 力 ， 上实 验课 时 ， 态度端 正 了 ， 做实 验非 常 认
能成 绩与 理论课 成绩 分开 ， 分为 １０ ， 满 ０ 分 包括 口试 、 操作 考核 、 时实 验成绩 ３ 分 ： １ 口试 占 ３ 分 。教 师 出 １ 平 部 （） ０ ０ 道 口试 题并 做 出标 准 答 案 ， 求 每 道 题 的 内容 比较 合适 ， 要 回答 的时 间 、 易程 度基 本相 同 。 口试 时设 ２ ３ 考 场 ， 难 ～ 个 每 个考 场 由 １ 名教 师 主 考 ， 每次 进 ２名 学生 ， 个学 生 考 每 ５ ｉ。学 生从 １ 道 题 中 随机 抽 出 １ 并 回答 ， 核 内容 ｍｎ ０ 题 考
fortran常见错误
fortran常见错误默认分类 2010-09-02 19:36:55 阅读80 评论0 字号：大中小订阅41 Insufficient virtual memory 虚拟内存不足70 Integer overflow 整数溢出错误71 Integer divide by zero 整数除0错误72 Floating overflow 浮点数溢出错误73 Floating divide by zero 浮点数除0错误74 Floating underflow 浮点数下溢错误75 Floating point exception 浮点数异常错误77 Subscript out of range 数组定义超出边界95 Floating-point conversion failed 浮点数格式转换失败146 Null pointer error 空指针错误147 Stack overflow 堆栈溢出148 String length error 字符串长度超出允许范围149 Substring error 数组下标超出允许范围150 Range error 整数值超出允许范围151 Allocatable array is already allocated 数组重复定义161 Program Exception - array bounds exceeded 引用数组下标超出允许范围162 Program Exception - denormal floating-point operand 非法浮点数操作符163 Program Exception - floating stack check 浮点数堆栈检查164 Program Exception - integer divide by zero 整数除0错误165 Program Exception - integer overflow 整数溢出166 Program Exception - privileged instruction 非法执行特权指令168 Program Exception - illegal instruction 非法指令170 Program Exception - stack overflow 堆栈溢出540 Array or substring subscript expression out of range 数组下标低下数组定义下界或高于数组定义上界541 CHARACTER substring expression out of range 字符串非法表示542 Label not found in assigned GOTO list 不属于GOTO语句引用的标号543 INTEGER arithmetic overflow 整数运算结果出现溢出544 INTEGER overflow on input 输入的整数值超出允许范围545 Invalid INTEGER 非法整数值546 REAL indefinite (uninitialized or previous error) 产生非法实数547 Invalid REAL 非法实数548 REAL math overflow 实数值溢出549 No matching CASE found for SELECT CASE select case语句中缺少case项550 INTEGER assignment overflow 整数定义超出允许范围556 A edit descriptor expected for CHARACTER 字符型数据的格式化输入和输出需要A编辑符557 E, F, D, or G edit descriptor expected for REAL 实数型数据的格式化输入和输出需要E,F,D,G编辑符558 I edit descriptor expected for INTEGER 整数型数据的格式化输入和输出需要I编辑符559 L edit descriptor expected for LOGICAL 逻辑型数据的格式化输入和输出需要L编辑符568 Multiple radix specifiers 输入或输出语句重复说明582 Array already allocated 数组已分配583 Array size zero or negative 数组大小为0或负数585 Array not allocated 没有被分配的数组610 Invalid argument 非法参数616 Invalid number in input 输入非法数字617 Invalid string in input 输入非法字符串618 Comma missing in COMPLEX input 输入的多个表达式之间缺少逗号619 T or F expected in LOGICAL read 输入的逻辑值必须是T或F622 Illegal character in hexadecimal input 输入非法的十六进制数637 Integer expected in format 格式语句中要求的整数638 Initial left parenthesis expected in format 格式语句中多余的左括号639 Positive integer expected in format 格式语句中要求用正整数641 Integer expected preceding H, X, or P edit descriptor 在H、X、P编辑符前要求用整数644 '.' expected in format 在D、E、F、G编辑符中w和d域之间用'.'分隔645 Unexpected end of format 格式语句没有结束646 Unexpected character in format 格式语句中的非法字符647 M field exceeds W field in I edit descriptor 在I编辑符中M域的值大于W域的值648 Integer out of range in format 格式语句中的整数值超出允许范围650 Separator expected in format 格式语句中需要分隔符663 Out of range: substring starting position 'pos' is less than 1 子字符串的起始位置小于1664 Out of range: substring ending position 'pos' is greater than string length 'len' 子字符串的终止位置大于字符串长度672 Out of memory 内存不足718 Cannot allocate temporary array -- out of memory 由于内存不足不能分配临时数组727 Cannot ALLOCATE allocatable array -- out of memory 由于内存不足不能分配数组729 DEALLOCATE failure: ALLOCATABLE array is not ALLOCATED 释放没有被分配的数组用fortran时曾经有个问题很头疼，就是如果输出到屏幕的话当程序结束时或者出错关闭的时候了窗口就一闪而过，根本来不及看输出了什么，当然你可以添加pause语句，但是如果迭代上千次后出错那加pause也不顶用了。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Visual Fortran 常见运行错误信息
41 Insufficient virtual memory 虚拟内存不足
70 Integer overflow 整数溢出错误
71 Integer divide by zero 整数除0错误
72 Floating overflow 浮点数溢出错误
73 Floating divide by zero 浮点数除0错误
74 Floating underflow 浮点数下溢错误
75 Floating point exception 浮点数异常错误
77 Subscript out of range 数组定义超出边界
95 Floating-point conversion failed 浮点数格式转换失败
146 Null pointer error 空指针错误
147 Stack overflow 堆栈溢出
148 String length error 字符串长度超出允许范围
149 Substring error 数组下标超出允许范围
150 Range error 整数值超出允许范围
151 Allocatable array is already allocated 数组重复定义
161 Program Exception - array bounds exceeded 引用数组下标超出允许范围
162 Program Exception - denormal floating-point operand 非法浮点数操作符
163 Program Exception - floating stack check 浮点数堆栈检查
164 Program Exception - integer divide by zero 整数除0错误
165 Program Exception - integer overflow 整数溢出
166 Program Exception - privileged instruction 非法执行特权指令
168 Program Exception - illegal instruction 非法指令
170 Program Exception - stack overflow 堆栈溢出
540 Array or substring subscript expression out of range 数组下标低下数组定义
下界或高于数组定义上界
541 CHARACTER substring expression out of range 字符串非法表示
542 Label not found in assigned GOTO list 不属于GOTO语句引用的标号
543 INTEGER arithmetic overflow 整数运算结果出现溢出
544 INTEGER overflow on input 输入的整数值超出允许范围
545 Invalid INTEGER 非法整数值
546 REAL indefinite (uninitialized or previous error) 产生非法实数
547 Invalid REAL 非法实数
548 REAL math overflow 实数值溢出
549 No matching CASE found for SELECT CASE select case语句中缺少case项
550 INTEGER assignment overflow 整数定义超出允许范围
556 A edit descriptor expected for CHARACTER 字符型数据的格式化输入和输出需要A编辑符
557 E, F, D, or G edit descriptor expected for REAL 实数型数据的格式化输入和输
出需要E,F,D,G编辑符
558 I edit descriptor expected for INTEGER 整数型数据的格式化输入和输出需要I编辑符
559 L edit descriptor expected for LOGICAL 逻辑型数据的格式化输入和输出需要L编辑符
568 Multiple radix specifiers 输入或输出语句重复说明
582 Array already allocated 数组已分配
583 Array size zero or negative 数组大小为0或负数
585 Array not allocated 没有被分配的数组
610 Invalid argument 非法参数
616 Invalid number in input 输入非法数字
617 Invalid string in input 输入非法字符串
618 Comma missing in COMPLEX input 输入的多个表达式之间缺少逗号
619 T or F expected in LOGICAL read 输入的逻辑值必须是T或F
622 Illegal character in hexadecimal input 输入非法的十六进制数
637 Integer expected in format 格式语句中要求的整数
638 Initial left parenthesis expected in format 格式语句中多余的左括号
639 Positive integer expected in format 格式语句中要求用正整数
641 Integer expected preceding H, X, or P edit descriptor 在H、X、P编辑符前要
求用整数
644 '.' expected in format 在D、E、F、G编辑符中w和d域之间用'.'分隔
645 Unexpected end of format 格式语句没有结束
646 Unexpected character in format 格式语句中的非法字符
647 M field exceeds W field in I edit descriptor 在I编辑符中M域的值大于W域的值
648 Integer out of range in format 格式语句中的整数值超出允许范围
650 Separator expected in format 格式语句中需要分隔符
663 Out of range: substring starting position 'pos' is less than 1 子字符串的
起始位置小于1
664 Out of range: substring ending position 'pos' is greater than string leng
th 'len' 子字符串的终止位置大于字符串长度
672 Out of memory 内存不足
718 Cannot allocate temporary array -- out of memory 由于内存不足不能分配临时
数组
727 Cannot ALLOCATE allocatable array -- out of memory 由于内存不足不能分配数组
729 DEALLOCATE failure: ALLOCATABLE array is not ALLOCATED 释放没有被分配的数组。