CV Error Messages

Number

CV Error Message

CV0013	access denied
	A specified file's permission setting does not allow the required access.
	One of the following may have occurred: An attempt was made to write to a read-only file. A locking or sharing violation occurred. An attempt was made to open a directory instead of a file.
CV1043	application output lost; screen exchange is off
	The program being debugged wrote to the display when the Flip (/F) or Swap (/S) was turned off. The program output was lost.
	Programs usually write to video page 0 by default. When flipping is on, video page 1 is usually reserved for CodeView. Programs that write to video page 1 must be debugged with swapping on.
	Turn Flip or Swap on to be able to view program output.
CV4011	assembler: divide by zero
	CodeView encountered a divide-by-zero error while assembling the current instruction.
CV4007	assembler: extra characters
	The instruction contained extra characters that could not be recognized. The instruction may have been mistyped.
	The line was ignored.
CV4008	assembler: illegal operand
	The wrong type of operand was used for this context.
	The instruction may have been mistyped.
CV4003	assembler: illegal range
	The size of a specified value exceeds the size expected by the instruction.
CV4010	assembler: illegal register
	An illegal or nonexistent register was accessed.
	The register name may have been mistyped.
	This error can be caused by trying to access 80386- or 80486-specific registers when CodeView is running on a 8088- or 80286-based machine.
CV4009	assembler: illegal segment
	An invalid segment was used.
CV4002	assembler: incorrect operand size
	An instruction required an operand of a different size.
CV4000	assembler: not enough operands
	Additional operands are required for this instruction.
CV4004	assembler: overflow
	Numeric overflow occurred while assembling the current instruction.
CV4005	assembler: syntax error
	The syntax for the current instruction is incorrect.
CV4001	assembler: too many operands
	Too many operands were specified for the most recently issued instruction.
CV4006	assembler: unknown opcode
	An instruction was not recognized.
	Check that the instruction was typed correctly.
CV3620	bad DLL format in filename
	CodeView did not recognize the format of the specified CodeView dynamic-link library (DLL) file.
	The DLL may be damaged or may be the wrong version.
	This error is caused if the specified file is not a DLL.
CV1006	breakpoint number or '*' expected
	A breakpoint was specified without a number or asterisk.
	A Breakpoint Clear (BC), Breakpoint Disable (BD), or Breakpoint Enable (BE) command requires one or more numbers to specify the breakpoints or an asterisk to specify all breakpoints.
	For example, the following command causes this error: bc rika
CV1068	breakpoint specifier is out of range
	A breakpoint number was specified that is higher than the number of current breakpoints.
CV4012	cannot assemble code with current execution model
	This error can be caused by trying to assemble p-code in CodeView.
CV1063	cannot create CURRENT.STS
	CodeView could not find an existing state file (CURRENT.STS), and CodeView tried to create one but failed.
	One of the following may have occurred: There was not enough space either on the disk containing the program to be debugged or on the disk pointed to by the INIT environment variable. There were not enough free file handles. Increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. The environment variable INIT pointed to a directory that does not exist.
CV5014	cannot execute function in watch expression
	A watch expression cannot specify a function to be executed.
CV3621	cannot find DLL filename
	CodeView could not find the specified dynamic-link library (DLL). This may be caused by a mistyped filename in the TOOLS.INI file.
CV3622	cannot load DLL filename
	CodeView was unable to load the specified dynamic-link library (DLL) file.
	Reinstall the DLL from the distribution disks.
CV3624	cannot load execution model filename: limit is 1
	Too many execution models are specified in the TOOLS.INI file.
	Only one execution model can be used at a time.
	Remove those execution models you are not using in your debugging session.
CV1065	cannot load expression evaluator filename
	CodeView could not load the specified expression evaluator.
	Make sure that filename is a valid expression evaluator DLL. If not, try reinstalling the CodeView DLLs from the distribution disks.
CV1066	cannot load expression evaluator filename; limit is 10
	Up to 10 expression evaluators can be specified in the TOOLS.INI file.
	Try removing expression evaluators you won't be using in your debugging session.
CV2404	cannot open response file filename
	The specified response file could not be opened.
	Check that the name of the file is spelled correctly and that the response file is correct.
CV5004	cannot read file
	CodeView could not open a file.
	Read the file again. If the second read fails, exit and restart CodeView. If the read process still fails, the file may be corrupt.
CV1054	cannot read this version of CURRENT.STS
	The state file (CURRENT.STS) has a version number that is not recognized by this version of CodeView.
	The old CURRENT.STS was ignored, and a new one will be created when CodeView exits.
CV2209	cannot restart; current process is not the process being debugged
	The debugging session was halted, and a different process was started.
	Return to the process being debugged by setting a breakpoint in it and issue a Go command.
CV5001	cannot select
	The cursor was not on the same line as an automatically selectable symbol.
CV2211	cannot terminate; current process is not the process being debugged
	The debugging session was halted, and a different process was current.
	Return to the process being debugged by setting a breakpoint in it and issue a Go command.
CV1056	cannot understand entry in filename
	At least one line in the given file (either the state file or the TOOLS.INI file) could not be interpreted.
	On startup, CodeView reads the state file (CURRENT.STS) and the TOOLS.INI file (if the latter is available).
	Examine the given file to find the problem.
CV0104	CodeView information for filename is newer than this version of CodeView
	The executable file was compiled or linked with a version of a Microsoft compiler that is newer than the version of CodeView you are using.
	You should try one of the following: Reinstall CodeView that came with the new compiler. Remove older versions of CodeView that may be present on your hard disk. Recompile the program with an older version of a Microsoft compiler.
CV2405	command-line option option invalid for target operating system
	The specified command line option was illegal in this context.
CV2206	corrupt CodeView information in filename; discarding
	This error can be caused by using mismatched versions of development tools. Verify that the versions of all tools are current and synchronized.
	Try recompiling the file with the /Zd switch (Prepare for Debugging option).
	This option produces an object file containing only public symbols (global or external) and line numbers.
CV1057	CURRENT.STS not found; creating
	Since the state file (CURRENT.STS) could not be located at startup, CodeView created a state file.
CV0008	executable file format error
	The system is not able to load the program to be debugged. The file is not an executable file, or it has an invalid format for this operating system.
	Try to run the program outside of CodeView to see if it is a valid executable file.
	This error can be caused if there is not enough memory available to run the program.
	Try making more memory available to the program.
CV1050	expression is not a memory address
	The expression does not evaluate to an address.
	For example, buffer[count] is a valid address because it points to a specific memory location. The logical comparison zed != 0 is not a valid address because it evaluates to TRUE or FALSE, not a memory address.
CV1067	extension missing for expression evaluator in filename in TOOLS.INI
	The Eval entry in the TOOLS.INI file expected a list of filename extensions.
CV1003	extra input ignored
	The first part of the command line was interpreted correctly.
	The remainder of the line could not be interpreted or was unnecessary.
CV1041	file error
	CodeView could not write to the disk.
	One of the following may have occurred: There was not enough space on the disk. The file was locked by another process.
CV1048	floating-point support not loaded
	An attempt was made to access the math processor registers in a program that does not use floating-point arithmetic.
	One of the following can cause this error: If the program does not perform floating-point calculations, this error can occur because the floating-point library code will not be loaded and cannot be used to access math processor registers. Math processor registers can only be accessed through the floating-point library code. If the program does not use floating-point instructions, this error can occur when you attempt to access the math processor before any floating-point instructions have been performed. The run-time library includes a floating-point instruction near the beginning so that the math processor registers are always accessible. If a floating-point instruction occurs in an assembly-language routine before such an instruction occurs in the high-level language code that calls the routine, this error occurs.
CV1250	general expression-evaluator error
	An error occurred in a CodeView expression evaluator.
	This error is probably caused by a lack of memory available to the expression evaluator. You can free memory by doing one or more of the following: Closing windows that are not needed. The Memory window, in particular, should be closed if possible. Delete breakpoints that are not needed. Disabling options that are not needed.
	As a last resort, exit CodeView and start the debugging session again.
	This error can also be caused by an expression that cannot be evaluated by the expression evaluator.
CV0014	invalid address
	The command expected an address but was given an argument that could not be interpreted as a valid address.
	A name or constant may have been specified without the period (.) that indicates a filename or line number.
CV1254	invalid address expression
	The expression entered does not evaluate to an address.
	For example, buffer[count] is a valid address because it points to a specific memory location. The logical comparison zed != 0 is not a valid address because it evaluates to TRUE or FALSE, not a memory address.
CV0022	invalid argument
	An invalid value was given as an argument.
CV1001	invalid breakpoint command
	CodeView could not interpret the breakpoint command.
	The command probably used an invalid symbol or the incorrect command format.
CV1062	invalid code-segment context change
	An attempt was made to set the IP register to a line or address in a different segment.
CV1046	invalid executable file: relink
	The executable file did not have a valid format.
	One of the following may have occurred: The executable file was not created with the linker released with this version of CodeView. Relink the object code using the current version of LINK.EXE. The .EXE file may have been corrupted. Recompile and relink the program.
CV1022	invalid flag
	An attempt was made to examine or change a flag, but the flag name was not valid.
	Any flags preceding the invalid name were changed to the values specified. Any flags after the invalid name were not changed.
CV4500	invalid format length; using variable length
	An invalid length was specified for the Memory window. CodeView will set the length based on the current window width.
	Try specifying a different length.
	Use the flag mnemonics displayed after entering the R FL command.
CV1027	invalid radix: specify 8, 10, or 16
	The Radix (N) command takes three radixes: 8 (octal), 10 (decimal), and 16 (hexadecimal). Other radixes are not permitted. The new radix is always entered as a decimal number, regardless of the current radix.
CV1004	invalid register
	The Register (R) command named a register that does not exist or cannot be displayed. CodeView can access the following registers:AXBXCXDXSPBPSIDIDSESSSCSIPFL
	When running under DOS or Windows on a 80386 or a 80486 machine, the 80386 registers option can be selected to access the following registers:EAXEBXECXEDXESPEBPESIEDIDSESFSCSGSSSEIPEFL
	When debugging p-code, CodeView can also access the following registers:

CV2210	invalid tab setting; using 8
	The value for tabs cannot be less than 0 or greater than 19. If you supply a value that is not in this range, the default tab value is 8.
CV4501	invalid window id
	The window ID was invalid. It must be either 0 or 1.
CV0005	I/O error
	An attempt was made to access an address that is not accessible to the program being debugged.
	Check the previous command for numeric constants used as addresses and for pointers used for indirection.
CV1042	library module not loaded
	The program being debugged uses load-on-demand dynamic-link libraries (DLLs). At least one of these libraries is needed but could not be found.
CV2207	loaded symbols for module
	CodeView automatically loaded the symbols for the given dynamic-link library (DLL). The DLL can now be debugged.
	This message is informational only and does not indicate an error.
CV1016	match not found
	A string could not be found that matched the search pattern.
CV1251	message
	An error occurred within a CodeView expression evaluator.
	No further explanation is available.
CV2401	missing argument for option option
	This error can be caused by splitting a response file line specifying a program to be debugged and its command-line options. The program and its command-line options must be on one line.
CV1051	missing or corrupt emulator information
	Status information about the floating-point emulator is missing or corrupt.
	The program probably wrote to this area of memory. Check that each pointer points to its intended object.
CV1023	no code at this line number
	A line number was specified but code was not generated for that line. This error can be caused by a blank line, comment line, line with program declarations, or line moved or removed by compiler optimization.
	To set a breakpoint at a line deleted by the optimizer, recompile the program with the /Od option to turn off optimization.
	Note that in a multiline statement the code is associated only with one line of the statement.
	This error can be caused by debugging a program whose source has been modified after it was compiled. Recompile the file before running it through CodeView.
CV0101	no CodeView information for filename
	The executable file or dynamic-link library (DLL) did not contain the symbols needed by CodeView.
	Be sure to compile the program or DLL using the /Zi option. If linking in a separate step, be sure to use the /CO option. Use the most current version of LINK.
CV1059	no CodeView source information
	A CodeView symbol listing for the source file or module being debugged does not exist.
	Be sure the file was compiled with the /Zi option or the /Zd option. If linking in a separate step, be sure to use the /CO option.
CV1255	no data members
	The class, structure, or union that was expanded did not have data members. A class must contain at least one data member to be expanded.
CV0000	no error condition
	You should not normally receive this error message since CV0000 indicates that no error occurred.
CV3626	no execution model; exiting
	CodeView needs an execution model in order to function.
	Check your TOOLS.INI file, and make sure there is a Native entry specified.
CV5013	no expression evaluators found; exiting
	CodeView needs at least one expression evaluator in order to operate.
	Check the [cv] or [cvw] section of your TOOLS.INI file and specify at least one Eval entry.
CV5005	no file selected
	A module must be selected before OK is chosen.
	To exit the dialog box without selecting a module, choose Cancel.
CV1011	no previous regular expression
	The Repeat Last Find command was executed, but a regular expression (search string) was not previously specified.
CV1061	no second monitor connected to system
	CodeView was invoked with the /2 option, but there was only one monitor for CodeView to use.
CV1031	no source lines at this address
	An attempt was made to view an address that does not have source code.
	This error can be caused by debugging a program whose source has been modified after it was compiled. Recompile the file before debugging it with CodeView.
CV1058	no source window open
	A command was entered to manipulate the contents of a Source window, but a Source window was not open.
CV0028	no space left on device
	The disk does not have any space available for writing.
	One of the following may have occurred: CodeView could not find room for writing a temporary file. An attempt was made to write to a disk that was full.
CV0002	no such file or directory
	The specified file does not exist or a path does not specify an existing directory.
	Check the file or directory name in the most recent command.
	One of the following may have occurred: The View Source (VS) command or the Open Source command from the File menu was used to view a nonexistent file. An attempt was made to print to a nonexistent file or directory.
CV0018	no such file or directory
	The specified file does not exist or a path does not specify an existing directory.
	Check the file or directory name in the most recent command.
	One of the following may have occurred: The View Source (VS) command or the Open Source command from the File menu was used to view a nonexistent file. An attempt was made to print to a nonexistent file or directory.
CV3630	no symbol handler found; exiting
	A symbol handler dynamic-link library (DLL) could not be found. The DLLs that CodeView uses must be in a location specified by the Cvdllpath entry in the [cvw] or [cv] section of TOOLS.INI.
CV3625	no transport layer; exiting
	CodeView needs a transport layer to make appropriate calls to the operating system in local debugging and to a remote computer in remote debugging.
	Check your TOOLS.INI file, and make sure there is a Transport entry in the [cv] or [cvw] CodeView section.
CV5009	no watch expression to delete
	An attempt was made to delete one or more watch variables (watch expressions), but watch expressions are not currently selected.
CV1039	not a text file
	An attempt was made to load a file that is not a text file. The file may be a binary data file or an executable program.
	This error can also occur if the first line of a file includes characters that are in the range of ASCII 0 to 8, 14 to 31, or 127 (0x0 to 0x8, 0xE to 0x1F, or 0x7F).
	The Source window can only be used to view text files.
CV0007	number of arguments exceeds DOS limit of 128
	CodeView is not able to restart the program that is being debugged because the number of arguments to the executable program exceeds the limit of 128.
CV0012	out of memory
	CodeView was unable to allocate or reallocate the memory that it required because not enough memory was available.
	Possible solutions include the following: Recompile without symbolic information in some of the modules. CodeView requires memory to hold information about the program being debugged. Compile some modules with the /Zd option instead of /Zi, or don't use either option. Remove other programs or drivers running in the system that could be consuming significant amounts of memory. Decrease the settings in CONFIG.SYS for FILES and BUFFERS.
CV3608	out of memory
	CodeView needed additional memory, but insufficient memory was available.
	Possible solutions include the following: Remove some drivers or applications that have been loaded in high memory. Recompile without symbolic information in some of the modules. CodeView requires memory to hold information about the program being debugged. Compile some modules with the /Zd option instead of /Zi, or don't use either option. Remove other programs or drivers running in the system that could be consuming significant amounts of high memory. Free some memory by removing terminate-and-stay-resident (TSR) software. Remove unneeded watch expressions or breakpoints.
CV1047	overlay not resident
	An attempt was made to access machine code from an overlay section of code that is not currently resident in memory.
	Execute the program until the overlay is loaded.
CV5012	packed executable file
	CodeView cannot step through the beginning of files that are linked with the /EXEPACK option. There are two solutions to this problem: Relink without this option to debug the file, and then switch back to linking with /EXEPACK for the release version of your program. Execute the program through startup code, and set breakpoints only after the program has entered main.
CV0003	program has terminated: restart to continue
	CodeView has detected a termination request by the program being debugged.
	The program cannot be executed because it has terminated and has not been restarted. Program memory remains allocated and may still be examined at this point.
	To run the program again, reload it using the Restart command.
CV1012	regular expression too long
	The regular expression was too long or complex.
	Use a simpler or more general regular expression.
CV0103	relink filename with current linker
	This version of CodeView expects the executable file to be in the format produced by the current version of the linker.
	Make sure PWB, NMAKE, or the compiler is not running an older version of the linker.
CV2403	response files cannot be nested
	A response file cannot refer to another response file.
CV1017	syntax error
	The command contained a syntax error.
	This error is probably caused by an invalid command or expression.
CV0024	too many open files
	CodeView could not open a file it needed because a file handle was not available.
	Increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=50 is the recommended setting.
	The program being debugged may have so many files open that all available handles are exhausted. Check that the program has not left files open unnecessarily. The first four handles are reserved by the operating system.
	Additional files can be made available by closing source windows. If more files are needed, set helpbuffers=0 in the [pwb] section of TOOLS.INI. As a result, Help cannot be used but several file handles will be made available.
CV1053	TOOLS.INI not found
	The directory listed in the INIT environment variable did not contain a TOOLS.INI file.
	Check the INIT variable to be sure that it points to the correct directory.
CV3629	too many execution models: choose one
	Only one execution model can be selected at a time.
	Additional execution models should be removed.
CV3628	too many transport layers selected: choose one
	Only one transport layer can be selected at one time.
CV1007	unable to open file
	The specified file cannot be opened.
	One of the following may have occurred: The file may not exist in the specified directory. The filename was misspelled. The file's attributes are set so that it cannot be opened. A locking or sharing violation occurred.
CV4502	unable to open the requested memory window
	CodeView could not open a Memory window.
	The only valid window IDs are 0 and 1. You may need to close some windows.
CV1021	unknown format specifier; specify one of A,B,I,IU,IX,L,LU,LX,R,RL,RT
	An unknown format specifier was given to a View Memory (VM), Memory Dump (MD), or Memory Enter (ME) command.
	The valid format specifiers are:

A	ASCII
B	byte
I	16-bit signed decimal integer
IU	16-bit unsigned decimal integer
IX	16-bit hexadecimal integer
L	32-bit signed decimal integer
LU	32-bit unsigned decimal integer
LX	32-bit hexadecimal integer
R	32-bit single-precision integer
RL	64-bit double-precision floating point
RT	80-bit 10-byte real (long double)

@ERP = This error is probably due to a mistyped command.

CV2402	unknown option option; ignored
	The specified option was not a valid option.
	Check that the option was typed correctly.
CV1018	unknown symbol
	The symbolic name specified could not be found.
	One of the following may have occurred: The specified name was misspelled. The wrong case was used when case sensitivity was on. Case sensitivity is toggled by the Case Sensitivity command from the Options menu or is set by the Option (O) Command-window command. The module containing the specified symbol may not have been compiled with the /Zi option to include symbolic information. A search was made for an undefined label or function.
CV0102	unpacked CodeView information in filename: use CVPACK
	For this version of CodeView, you must process all executable files using CVPACK, which compresses the debugging information in the file.
	Pass the file through CVPACK.EXE before starting CodeView.
CV1040	video mode changed without /S option
	The program being debugged changed screen modes, and CodeView was not set for swapping. The program output is now damaged or unrecoverable.
	To be able to view program output, exit CodeView and restart it with the Swap (/S) option.
CV1064	window could not be opened
	CodeView tried to open a window, but failed to do so.
	This error is probably caused by a lack of memory available to CodeView.
	Exit CodeView and make more memory available, then restart CodeView.
CV3623	wrong DLL filename
	CodeView expected one type of dynamic-link library (DLL) but read in a different type. This error is probably caused by specifying an incorrect filename in the TOOLS.INI file. For example, you may have specified an execution model DLL in the expression evaluator entry.