that included an I/O list had no field descriptors to use in transferring those values. severe or info 3 (61): Format/variable-type mismatch FOR$IOS_FORVARMIS 2. An attempt was made either to read or write a real variable with an integer field descriptor (I, L, O, Z, B), 61 or to read or write an integer or logical variable with a real field descriptor (D, E, or F). To suppress this error message, see Section 3.15. severe (62): Syntax error in format 62 FOR$IOS_SYNERRFOR. A syntax error was encountered while the RTL was processing a format stored in an array or character variable. error or info 3 (63): Output conversion error FOR$IOS_OUTCONERR 2. During a formatted output operation, the value of a particular number could not be output in the specified field length without loss of significant digits. When this 63 situation is encountered, the overflowed field is filled with asterisks to indicate the error in the output record. If no ERR address has been defined for this error, the program continues after the error message is displayed. To suppress this error message, see Section 3.16. severe (64): Input conversion error FOR$IOS_INPCONERR 2. During a formatted input operation, an 64 invalid character was detected in an input field, or the input value overflowed the range representable in the input variable. The value of the variable was set to zero. error (65): Floating invalid FOR$IOS_FLTINV. During an arithmetic operation, the floating-point values used in a calculation were invalid for the type of operation requested or invalid exceptional values. For 65 example, when requesting a log of the floating-point values 0.0 or a negative number. For certain arithmetic expressions, specifying the -check nopower option can suppress this message (see Section 3.17). For information on allowing exceptional IEEE values, see Section 3.33. severe (66): Output statement overflows record 66 FOR$IOS_OUTSTAOVE. An output statement attempted to transfer more data than would fit in the maximum record size. severe (67): Input statement requires too much data FOR$IOS_INPSTAREQ. Attempted to read more data than exists in a 67 record with an unformatted READ statement or with a formatted sequential READ statement from a file opened with a PAD specifier value of ' NO ' . severe (68): Variable format expression value error FOR$IOS_VFEVALERR 2. The value of a variable format expression was not within the range acceptable for its intended use; for example, 68 a field width was less than or equal to zero. A value of 1 was assumed, except for a P edit descriptor, for which a value of zero was assumed. error (69): Process interrupted (SIGINT) 69 1 FOR$IOS_SIGINT. The process received the signal SIGINT. Determine source of this interrupt signal (described in signal(3) ). severe (70): Integer overflow FOR$IOS_INTOVF. During an arithmetic operation, an integer value byte, word, or longword range. The result of the operation 1exceeded 70 was the correct low-order part. See Chapter 9 for ranges of the various integer data types. Consider specifying a larger integer data size (modify source program or, for an INTEGER declaration, possibly use the f90 option -integer_size nn ). severe (71): Integer divide by zero FOR$IOS_INTDIV. During an integer arithmetic operation, an 71 1 attempt was made to divide by zero. The result of the operation was set to the dividend, which is equivalent to division by 1. error (72): Floating overflow FOR$IOS_FLTOVF. During an arithmetic operation, a floating-point 72 1 value exceeded the largest representable value for that data type. See Chapter 9 for ranges of the various data types. error (73): Floating divide by zero 73 1 FOR$IOS_FLTDIV. During a floating-point arithmetic operation, an attempt was made to divide by zero. 74 1 error (74): Floating underflow FOR$IOS_FLTUND. During an arithmetic operation, a floating-point value became less than the smallest finite value for that data type. Depending on the values of the -fpe n option (see Section 3.33), the underflowed result was either set to zero or allowed to gradually underflow. See Chapter 9 for ranges of the various data types. error (75): Floating point exception FOR$IOS_SIGFPE. A floating-point exception occurred. Core dump file created. Possible causes include: Division by zero 75 1 ? Overflow ? Invalid operation, such as subtraction of infinite values, multiplication of zero by infinity (without signs), division of zero by zero or infinity by infinity ? Conversion of floating-point to fixed-point format when an overflow prevents conversion ? error (76): IOT trap signal FOR$IOS_SIGIOT. Core dump file created. Examine core dump for 76 1 possible cause of this IOT signal. For more information about signals, see Section 8.3. severe (77): Subscript out of range 77 1 FOR$IOS_SUBRNG. An array reference was detected outside the declared array bounds. error (78): Process killed (SIGTERM) FOR$IOS_SIGTERM. The process received the signal SIGTERM. 78 Determine source of this software termination signal (described in signal(3) ). error (79): Process quit (SIGQUIT) 1FOR$IOS_SIGQUIT. The process received the signal SIGQUIT. Core 79 dump file created. Determine source of this quit signal (described in signal(3) ). 1info (95): Floating-point conversion failed 95 1 FOR$IOS_FLOCONFAI. The attempted unformatted read or write of nonnative floating-point data failed because the floating-point value: Exceeded the allowable maximum value for the equivalent native format and was set equal to infinity (plus or minus) ? Was infinity (plus or minus) and was set to infinity (plus or minus) ? Was invalid and was set to not a number (NaN) ? Very small numbers are set to zero (0). This error could be caused by the specified nonnative floating-point format not matching the floating-point format found in the specified file. Check the following: The correct file was specified. ? The record layout matches the format DIGITAL Fortran 90 is expecting. ? The ranges for the data being used (Chapter 9) ? The correct nonnative floating-point data format was specified (Chapter 10). ? severe (108): Cannot stat file 108 FOR$IOS_CANSTAFIL. Attempted stat operation on the indicated file failed. Make sure correct file and unit were specified. severe (120): Operation requires seek ability FOR$IOS_OPEREQSEE. Attempted an operation on a file that requires 120 the ability to perform seek operations on that file. Make sure the correct unit, directory path, and file were specified. severe (130): User breakpoint (SIGTRAP) FOR$IOS_BRK_USERBP. Break exception generated a SIGTRAP signal 130 1 (described in signal(3) ). Core dump file created. Examine core dump for possible cause. severe (131): Kernel breakpoint (SIGTRAP) Break exception generated a SIGTRAP signal 1FOR$IOS_BRK_KERNELBP. 131 (described in signal(3) ). Core dump file created. Examine core dump for possible cause. 135 severe (135): User single step (SIGTRAP) 1
相关推荐：
loading