The following messages may be generated at run time when your program has serious errors.
| R6000 |
stack overflow |
| |
The program has run out of stack space. This can occur when a program uses a large amount of local data or is heavily recursive. |
| |
Recompile using the /F compiler option, or relink using the linker /STACK option to allocate a larger stack. |
| R6001 |
null pointer assignment |
| |
The contents of the NULL segment have changed in the course of program execution. The program has written to this area, usually by an inadvertent assignment through a null pointer. |
| |
The NULL segment is a location in low memory that is not normally used. The contents of the NULL segment are checked upon program termination. If a change is detected, the error message is printed and the exit code is 255. |
| |
Note that the program can contain null pointers without causing this error. The error appears only when the program writes to memory through a null pointer. It reflects a potentially serious error in the program. Although a program that produces this error may appear to operate correctly, it may cause problems in the future and may fail to run in a different operating environment. |
| R6002 |
floating-point support not loaded |
| |
The program needs the floating-point library, but the library was not loaded. |
| |
This occurs in two situations:
1.The program was compiled or linked with an option (such as /FPi87) that required an 8087/287/387 coprocessor, but the program was run on a machine that did not have a coprocessor installed.
Either recompile the program with the /FPi option or install a coprocessor.
2.A format string for one of the routines in the printf or scanf families contains a floating-point format specification, and there are no floating-point values or variables in the program. The compiler attempts to minimize the size of a program by loading floating-point support only when necessary. Floating-point format specifications within format strings are not detected, so the necessary floating-point routines are not loaded.
Use a floating-point argument to correspond to the floating-point format specification, or perform a floating-point assignment elsewhere in the program. This causes floating-point support to be loaded.
|
| R6003 |
integer divide by 0 |
| |
An attempt was made to divide an integer by 0, giving an undefined result. |
| R6005 |
not enough memory on exec |
| |
Not enough memory remained to load the program being spawned. |
| |
This error occurs when a child process spawned by one of the exec library routines fails and the operating system cannot return control to the parent process. |
| R6006 |
invalid format on exec |
| |
The file to be executed by one of the exec functions was not in the correct format for an executable file. |
| |
This error occurs when a child process spawned by one of the exec library routines fails and the operating system cannot return control to the parent process. |
| R6007 |
invalid environment on exec |
| |
During a call to one of the exec functions, the operating system found that the child process was given an invalid environment block. |
| |
This error occurs when a child process spawned by one of the exec library routines fails and the operating system cannot return control to the parent process. |
| R6008 |
not enough space for arguments |
| |
There was enough memory to load the program but not enough room for the argv vector. |
| |
There are several ways to correct this problem:
 Increase the amount of memory available to the program.
Reduce the number and size of command-line arguments.
Reduce the environment size, removing unnecessary variables.
Rewrite either the _setargv or the _setenvp routine.
|
| R6009 |
not enough space for environment |
| |
There was enough memory to load the program but not enough room for the envp vector. |
| |
There are several ways to correct this problem:
Increase the amount of memory available to the program.
Reduce the number and size of command-line arguments.
Reduce the environment size, removing unnecessary variables.
Rewrite either the _setargv or the _setenvp routine.
|
| R6010 |
abnormal program termination |
| |
This error is displayed by the abort( ) routine. The program terminates with exit code 3, unless an abort( ) signal handler has been defined by using the signal( ) function. |
| R6012 |
illegal near-pointer use |
| |
A null near pointer was used in the program. |
| |
This error occurs only if pointer checking is in effect. Pointer checking is set with the /Zr option or the check_pointer pragma. |
| R6013 |
illegal far-pointer use |
| |
An out-of-range far pointer was used in the program. |
| |
This error occurs only if pointer checking is in effect. Pointer checking is set with the /Zr option or the check_pointer pragma. |