13 ERROR MESSAGES

13.1 What this Chapter Covers

The following is a list of common user error messages, and some suggested ways to solve the problem.

CrossView Pro is a complex program running on several hosts. From time to time, slight differences between the documentation and the program's operations do occur. The list of errors presented below and the suggested remedies may not be, therefore, entirely comprehensive.

If you get a message that begins with "XVW Error" or "XVW Fatal Error" please contact TASKING technical support for help.

13.2 Error Messages

(in alphabetical order):

"member-name" is not defined for "enum enum"

You cannot assign or compare an enum type with a name that is not in the enumeration's members. Try casting the enum to a different type.

'save' must have a filename; type 'help save' for more information

The save command requires a file to be supplied. Note: if the supplied file name already exists, it will be overwritten.

*** Fatal XVW error

CrossView Pro has detected a error which it can not handle. If information is displayed, you may be able to detect the source of the error and correct it. Otherwise, if the message persists, please contact TASKING Technical Support.

0xvalue is an invalid value. The register register is unchanged.

The value supplied is incorrect for the specified register. Verify that both the value and the register are correct and retry.

Adding 2 pointers not allowed

You cannot add two pointers together in an expression. If you intended to add to a pointer, make sure that the argument is a value, not another pointer.

Address not allowed for '! or ~ or % operator'

The "Not", "One's complement", and "Modulus" operators cannot be used with an address. If you intended to perform the operation on the contents of the address, please be sure to dereference the pointer.

Addresses not allowed in '* or / operator'

The multiply and divide operators cannot be used with address data. If you intended to perform the operation on the contents of the address, please be sure to dereference the pointer.

Addresses not allowed in 'bitwise logical or logical or shift operators'

Bitwise logical (&, ^, or |), logical (&& or ||), and shift (<< >>) operators only work on data, not addresses. If you intended to perform the operation on the contents of the address, please be sure to dereference the pointer.

Attempt to set breakpoint at invalid address

The memory location is not available. If the memory location is not out of the target chip's range, you may need to map the target system's memory to allow access to this location.

Bad argument to the command command

The argument you have given to the sio or f command is not allowed. Refer to the Command Reference chapter, for allowable arguments and their meanings.

Bad assertion number: number

The number number is not a valid assertion number. List assertions with the l a (list assertions) command to determine which assertion numbers are valid.

both expressions must be addresses for 'relational operator'

If one of the expressions is an address type, both expressions for relational operators (<, <=, >, >=, ==, and !=) must be address types. Retry with both expressions as either addresses or arithmetic types.

Breakpoint is (or at the address of) an CrossView internal breakpoint. It can not be deleted.

You may not install a breakpoint over an CrossView Pro internal breakpoint. See Breakpoints and Assertions chapter for more information.

com return code=code

The MS-DOS version of CrossView Pro received a status condition from the monitor communication channel which it can not handle. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

command takes no arguments.

The command command needs no arguments. Refer to the Command Reference chapter, for the command syntax.

Can not open file (file)

CrossView Pro could not open the file file. Check the spelling of file and check that the file is in the correct directory. You should also check the permission of file. With MS-DOS, check the CONFIG.SYS file for the maximum number of open files allowed. Increase the number and reboot if necessary.

Can not output to input stream

An attempt was made to output to an input stream. The most common case is incorrectly setting up your simulated i/o streams. Correct and retry.

Can not scroll that window

The window you have tried to scroll is not scrollable. Examine your choice of window and/or your choice of windowing commands.

Can't define macro: out of space

There is not enough host memory to add your macro. Eliminate one or more unused macros before adding a new one.

Can't expand macro: out of space

There is not enough host memory to expand your macro. Eliminate one or more unused macros before adding a new one.

Can't monitor data: out of space

CrossView Pro cannot add any more variables or expressions to monitor. You must delete one or more variables or expressions before adding any more.

Can't open logfile-name as log file

CrossView Pro could not open the specified host-to-target system communications logfile. Check the spelling of logfile-name and that logfile-name is in the correct directory. Check permissions of logfile-name. With MS-DOS, check the CONFIG.SYS file for the maximum number of open files allowed. Increase the number and reboot if necessary. Make sure the filename is valid for the host Operating System.

Can't open output-file-name as output file

CrossView Pro could not open the specified output file. Check the spelling of output-file-name and that output-file-name is in the correct directory. Check permissions of output-file-name. With MS-DOS, check the CONFIG.SYS file for the maximum number of open files allowed. Increase the number and reboot if necessary. Make sure the filename is valid for the host operating system.

Can't open playback-file-name as playback file

CrossView Pro could not open the specified playback file. Check the spelling of playback-file-name and that playback-file-name is in the correct directory. Check permissions of playback-file-name. With MS-DOS, check the CONFIG.SYS file for the maximum number of open files allowed. Increase the number and reboot if necessary. Make sure the filename is valid for the host operating system.

Can't open record-file-name as record file

CrossView Pro could not open the specified recording file. Check the spelling of record-file-name and that record-file-name is in the correct directory. Check permissions of record-file-name. With MS-DOS, check the CONFIG.SYS file for the maximum number of open files allowed. Increase the number and reboot if necessary. Make sure the filename is valid for the host operating system.

Can't open file 'file'

CrossView Pro could not open the specified file. Check the spelling of file and that file is in the correct directory. Check permissions of file. With MS-DOS, check the CONFIG.SYS file for the maximum number of open files allowed. Increase the number and reboot if necessary. Make sure the filename is valid for the host operating system.

Can't perform trace, out of memory

There is not enough host memory to support tracing. Reduce memory demands and retry again. If the problem persists, please contact the TASKING Technical Support staff for assistance.

Can't set breakpoint; either the current file has no symbols, or line line# is not inside any procedure in the current file.

CrossView Pro was unable to set the breakpoint that you specified. First check the location of line line# and verify that it is in the current procedure being debugged. If it is within the current procedure, then you may need to compile/assemble/link/locate for debugging. Refer to chapter Overview for details.

Can't start a new process. Feature not implemented.

Your host system does not support shell commands. Any attempt to issue shell commands will cause this message to be displayed.

Can't write to a read-only SFR.

The SFR register is a read-only register. It can not be set or altered.

Cannot allocate memory for symbol table

Allocating memory for storing the symbol table failed. Remove some tasks from memory or add more memory to your computer system.

Cannot allocate symbol table memory buffers

The symbol table is too large for CrossView Pro. You may need to selectively compile with the -g switch only those files and procedures that most interest you.

Cannot allow that combination of operand(s) and operator

The operand(s) is/are incompatible for this type of operation. For example, you may not add two structures. Please verify the operation and data types you are using.

Character constant is missing ending '

Character constants must be delimited with single quotes. Example: 'a'.

Command 'command' not allowed while emulator running in background

The target is running, this command is not allowed unless the target is stopped. See the st command.

couldn't error-message

VMS is reporting a condition that CrossView Pro can not handle. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Data already being monitored "task-id":`symbol '

The variable or expression symbol is already being monitored by CrossView Pro. You do not need to enter it again.

Display format required

The display command expected an output format option that was not supplied. See chapter CrossView Command Language for valid format options and their meanings.

Double not allow in '% or ~ operator'

You may not use the one's complement or modulus operators on double floating point types.

Double not allow in 'bitwise operator'

You may not use bitwise operators (&, ^ and |) on double floating point types.

ERROR: you must enter ?,i,r,d

CrossView Pro's line editor only supports the following commands: ?-help, i-insert, r-replace, d-delete, and <cr> to execute command.

Establish a file context first.

The command executed requires an active file. Verify the file you specified to CrossView Pro on start up.

Establish a procedure context first

The command executed requires an active procedure. Either execute the command from within a procedure, or give a procedure name as an argument to the command.

Exiting procedure call state

An unknown system signal caused the end of a command line function call.

Expecting stream number

The following forms of the sio command expect a stream number:
stream sio {i| o} {file|screen}
stream sio d
stream sio p prompt

Expression garbaged

The symbol table contains a type that is unknown to CrossView Pro. Please verify that you are using the compiler and utilities supplied to you. If the condition persists, please contact the TASKING Technical Support staff for assistance.

file has already been edited, going to NEW file

The command executed requires that the file be edited only once. A new file has been created.

failed to allocate the SIO tables

Entries for recording simulated input/output information could not be allocated due to lack of host memory. Please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Float not allowed in '% or ~ operator'

You may not use the modulus or one's complement operators on floating point types. Change the data type to an appropriate type, for example, integer.

Float not allowed in 'bitwise or shift operator'

You may not use the bitwise (&, ^, or |) or shift (>>, or <<) operators on floating point types. Change the data type to an appropriate type, for example, integer.

Framing Error on COM port number

The host computer detected a data frame communication error on COM port number. Check the host and target communication set up as well as line connections. If the problem persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

I can't put something that big in the child process

The size of the expression exceeds the buffer size needed to spawn a child process. Be sure you have linked end.c in your application. This module implies space for CrossView Pro in your execution environment. Refer to section Building Your Executable in chapter Overview. If this condition persists, please contact the TASKING Technical Support staff for assistance.

I don't have symbols for this procedure

You will need to re-compile, assemble, link and locate with the proper debugging options before using this command. See section Building Your Executable in chapter Overview for details.

I have no source file for this address

The program counter holds an address which is outside all the address ranges that CrossView Pro knows about. This may happen if program execution has reached a file that was not compiled with the -g generate debug symbols switch.

I need a linenumber

The go g command requires a line number. Enter a line number and the command will be executed.

Illegal address for Emulator Hardware Breakpoint

The address specified is out of emulator hardware breakpoint memory range. Verify the address and retry.

Illegal argument ("0") to 'p' command

You must specify a number greater than 0 for the p command, which prints the specified number of lines.

Illegal argument to 'command' command: 'argument'

You have passed an illegal argument to the specified command. Refer to chapter Command Reference for legal arguments.

Illegal argument to ct: 'argument'

You have passed an illegal argument to the C-trace command. Refer to chapter Command Reference for legal arguments.

Illegal data monitor command

You have passed an illegal argument to the m data monitor command. Legal commands are:
m exp to set up monitoring
id m d to delete monitoring of a specific expressions
m d to delete monitoring of all expressions

Illegal third arg to set: 'argument'

The set command may have only two arguments: the name by which the macro is known and the command string to be executed when the macro is invoked. Enclose the command string in quotes, separating the individual commands with semicolons. Refer to chapter Command Reference for more information.

Improper floating point format length

You have specified a format length that is inconsistent with floating numbers. Legal lengths are 4 and 8 bytes.

Improper integer format length

You have specified a format length that is inconsistent with integer numbers. Legal length are 1, 2, and 4 bytes. You may also choose b, s, or l for 1, 2, and 4 byte integers.

Improper string format length

You have specified a format length that is inconsistent with character strings. Choose a positive number.

Input buffer overflow

CrossView Pro is over-running the input buffer. Contact your system administrator to either increase the input buffer or lower the communication line baudrate.

Input communications buffer overflow on COM port

CrossView Pro is over-running the input buffer. Contact your system administrator to either increase the input buffer or lower the communication line baudrate.

Input from stdin longer than max-input-size characters: input-string
Command truncated

The input data is longer that the input buffer, therefore the data was truncated at max-input-size. Try to reduce the input data and/or commands.

Internal error while setting an instruction level breakpoint

If this error condition persists, please contact the TASKING Technical Support staff for assistance.

Invalid assertion maintenance command

You have entered an illegal assertion command. Valid commands are:
a a to activate assertions
a d to delete assertions
a s to suspend assertions

Invalid value for uplevel break.

You have entered an illegal value for an uplevel break. The form of the command is exp bU or exp bU, where exp determines how many returns from functions should occur before the break. Execute the t command to find out how many levels down in the stack you are, then choose an appropriate value for the uplevel break. See chapter Command Reference for more information.

Invoking procedure calls not allowed while emulator is running in the background

The target is running, this command is not allowed unless the target is stopped. See the st command.

Macro Expansion error: expansion looping

CrossView Pro looped 50 times while trying to expand this macro without completing the expansion. Check the logic of the macro arguments. It may need to be corrected or simplified.

Macro Expansion error: expansion too large

The macro expansion exceeds 200 commands. The macro must be simplified.

Macro Expansion error: missing '('

See the command reference page or use the help command to review macro command syntax.

Macro Expansion error: missing ')'

See the command reference page or use the help command to review macro command syntax.

Macro Expansion error: missing ','

See the command reference page or use the help command to review macro command syntax.

Macro Expansion error: not enough args

See the command reference page or use the help command to review macro command syntax.

Macro Expansion error: out of space

There is not enough memory to expand the macro. Eliminate one or more unused macros before adding a new one.

Maximum trace size is: max-trace-size

CrossView Pro can perform C tracing only up to max-trace-size source lines. Choose a number less than max-trace-size with the ct command.

Missing { after if command

The required format for the if command is: if exp {commands}

Missing file name or 'screen'

The sio command was missing a required parameter for setting up a simulated i/o stream. See chapter Command Reference for command definition and format.

Missing format character

You did not specify a display format type with your command. Either remove '/' from the command, or add a format character.

Missing prompt string

You did not specify a prompt string with the sio command. Either remove p from the sio command, or add a prompt string.

Must supply 'b' or 'f'

The color command requires a value of f for foreground or b for background to modify the screen color.

Must supply 'r','w' or 'b'

Both the data range (bD) and data (bd) breakpoint commands require the type of data modification to generate a break condition. Use r for read, w for write, and b for both read/write. Please see chapter Command Reference for more information.

Must supply data to be monitored

You did not specify a variable or expression to the m monitor command. Please provide a variable or expression to be monitored, for example, m myvar.

Must supply second address with bD command.

The bD command requires two addresses. Either specify an upper limit if you want to break anywhere in memory range, or use the bd command if you want to break on an individual address.

Negative /baudrate value ignored. (VAX)
or
Negative baud rate (-S) value ignored.

The baudrate specified was a negative value. Please specify a legal value or use the default.

Negative /TIMEOUT value ignored. (VAX)
or
Negative timeout interval (-I) value ignored.

The time out value specified was negative. Please specify a legal timeout value or use the default.

No child process

The CrossView Pro internal data structure containing user information about child processes is not as expected. Please contact the TASKING Technical Support staff for assistance.

No current file

Undefined special variable, $file; probably due to debugging where no symbols are present.

No current line number

Undefined special variable, $line; probably due to debugging where no symbols are present.

No current procedure

Undefined special variable, $proc; probably due to debugging where no symbols are present.

No host memory

There is not enough space in memory to execute this command. Check whether you have unnecessary processes running in the background or resident in memory.

No host memory for command

There is not enough space in memory to execute this command. Check whether you have unnecessary processes running in the background or resident in memory.

No macros to save; file not created

CrossView Pro found no macros to save, therefore the save command did not create a file.

No Match - pattern

CrossView Pro did not find the specified pattern in its search of this file. Check your spelling or case-sensitivity. Use the Z command to toggle case-sensitivity if necessary.

No memory space

There is not enough host memory to execute this command. Check whether you have unnecessary processes running in the background or resident in memory.

No more hardware breakpoints available

The target system uses hardware breakpoints to support the data breakpoint function. To continue, you must explicitly delete a data breakpoint before placing a new one.

No more room for directories (> max-dir-size)

You can reference no more that max-dir-size directories for source files.

No more SIO windows, I/O to command window.

Only four SIO streams can be displayed simultaneously in the SIO window. Subsequent SIO streams' output will be displayed in the command window.

No name of symbol file specified

CrossView Pro cannot deduce the name of a symbol file. No filename was given to the N command and no symbol file was currently loaded.

No playback name specified

Give the name of the playback file to be used for this session.

No process

CrossView Pro only allows one process to be debugged at the same time.

No such breakpoint

The breakpoint number was incorrect. List breakpoints with the l b command to find the correct breakpoint.

No such field name "name" for "<structure | union> name"

The field name is not recognized for the specified structure or union. Check the spelling of field name. The /t format will show you the names and types of a particular structure's or union's fields.

No Such Line

CrossView Pro can not find the specified line number in any of its known files. Please check the source window or a source listing for legal line numbers.

No such procedure, "name".

CrossView Pro does not recognize name as a procedure name. Check the spelling and whether the file was compiled/assembled/linked/located for debugging. Check that the file is in the appropriate directory.

No such procedure or file name: procedure

CrossView Pro does not recognize procedure as a procedure or file name. Check the spelling and whether the file was compiled/assembled/linked/located for debugging. Check that the file is in the appropriate directory.

No such PSW register state

Check register name and selected target.

No such register

The target processor does not have a register with that name.

No such sr reg state

Check register name and selected target.

No such stream

The stream you tried to delete does not exist. Check the stream number, correct, and retry.

No symbols - unable to determine end-of-procedure

CrossView Pro has no symbol information for this procedure. To facilitate debugging this procedure, you must compile, assemble, link and locate with the appropriate switches. Refer to the Overview chapter for details.

No symbols available in active procedures.

To get symbol information you must compile, assemble, link, and locate with the appropriate switches. Refer to the Overview chapter for details.

No symbols for that procedure

To get symbol information you must compile, assemble, link, and locate with the appropriate switches. Refer to the Overview chapter for details.

No User or System special variable matches prefix name

The string argument of the l s command did not match any user or system special defined variables. Check spelling and case-sensitivity and retry. You may also enter l s to print out all the user and system special defined variables.

Not enough memory available to start up windows. Either use the -nw (no window) option or remove resident programs from memory.

CrossView Pro has detected that there is not enough host memory to execute the windowing software. You may need to use the -nw option to start up CrossView Pro in line mode. Check whether you have unnecessary processes running in the background or resident in memory.

Not enough memory to execute shell command.

The attempt to create a child process for the shell command failed due to the lack of host memory. Check whether you have unnecessary processes running in the background or resident in memory.

Not enough memory to start window mode

CrossView Pro has detected that there is not enough host memory to execute the windowing software. You may need to use the -nw option to start up CrossView Pro in line mode. Check whether you have unnecessary processes

Not enough space

CrossView Pro has detected a general error due to lack of host memory. Check whether you have unnecessary processes running in the background or resident in memory.

Not in known territory. Could not set breakpoint.

CrossView Pro's current location is not in a file or procedure that it knows about. The breakpoint request can not be performed.

Not in window mode

The command issued requires CrossView Pro windows to be active. Use the WW command and repeat the previous command.

Not that many levels active on the stack.

A stack level was specified that does not exist. Execute the t command to determine levels on the stack. See chapter Command Reference for more information.

Oops called with sig = signal-number

CrossView Pro has received a signal that it can not handle. Continuing from this point may result in a fatal process condition. If this condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Placement of the breakpoint handler must be in one of
the restart vectors. Choose a value from 0 to 7.
Try again. (Hit <cr> to exit)?

The specified placement for the breakpoint handler was not valid for this target. CrossView Pro is requesting a valid location.

Procedure "name" is not active on the stack.

The procedure name was not found on the current stack. Execute the t command to list functions which are active on the stack.

Procedure 'name' is not at that stack depth

The procedure name was not found on the specified stack. Execute the t command to list functions which are active on the stack.

Procedure "procedure" is not active

The procedure procedure was not found on the current stack. Execute the t command to list functions which are active on the stack or l p for list of procedures known to CrossView Pro.

Program not completely loaded

An error occurred during loading a symbol file. Check what cause the problem (illegal filename or file format). You may retry to load a symbol file.

Prompt too long (> max-number)

Choose a prompt of no more than max-number characters.

Ran out of memory reading symbol file into memory

Reduce the size of the symbol file by re-compiling only the "interesting" files with the -g debug switch.

Read I/O request could not be queued

VMS detected an error for a read I/O queue which CrossView Pro can not handle. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Readprompt I/O request could not be queued

VMS detected an error for a read I/O queue which CrossView Pro can not handle. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Redo: line too large

Limit line length to fewer than 256 characters.

Result type too large for command line call.

A command line function call must pass the result back in a register. The specified function does not. You cannot call functions whose return value is greater than an integer, for instance floating point types and structures.

Result type undefined

Type casting from the expression or variable to the result type was not possible.

Second address smaller then first

When specifying a range of addresses for a data breakpoint, the second address must be higher than the first.

Sim I/O request too long (>max-number bytes)

The I/O request exceeds the maximum length.

Simulated I/O stream out of range

Choose a stream value between 0 and 7.

Sorry, the "v" command is not supported on this host

No visual editor is available on this host.

Stream already active

Either choose another stream, or deactivate this one before re-assigning it.

String constant is missing ending "

String constants must be delimited with double quotes: "

Subtracting 2 pointers not allowed

You cannot subtract two pointers in an expression. If you intended to subtract from a pointer, make sure that the argument is a value, not another pointer.

Symbol file is either unreadable or too short

The symbol file is not an absolute IEEE-695 file, or the file format is not correct, or the file is not an IEEE-695 file at all.

Symbol file is not formatted correctly

The symbol file is not intended for the type of microprocessor you are using.

Symbol not in current procedure

There is no symbol by this name in the current procedure. Check the spelling of the symbol name.

The 'command' command accepts no args

The command command does not accept any arguments. See chapter Command Reference for more information on command.

The window would be too large; Total lines must not be greater that max-size

The window size options specified would create a window that would have exceeded the screen size. Retry with corrected window size options.

There is insufficient information to do a structure dump

CrossView Pro cannot uniquely identify the structure or part of the structure to be dumped.

There is no associated source.

The program counter holds an address which is outside all the address ranges that CrossView Pro knows about. This may happen if program execution has reached a file that was not compiled with the -g debug switch.

There is no available source line for the current address.
$pc= address

CrossView Pro is reporting that the current position has no associated source line. This may happen if you are trying to debug a routine that was not compiled with -g debug switch or are trying to debug a runtime library routine.

This does not appear to be a struct or a union

The data entered is not recognizable as a structure or union. Check the specified variable.

Timed read I/O request could not be queued

VMS reported a condition on a timed read i/o request that CrossView Pro could not handle. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Too many args to unset: 'argument'

You may specify only one macro at a time, for example, unset name, or you may remove all macros at once with unset.

Too many assertions (>max-number)

The maximum number of assertions allowed is max-number as shown in the error message. Remove a previous assertion before trying to add one, or reinvoke CrossView Pro with the -a option to increase the maximum number of assertions.

Too many breakpoints (> max_number)

The maximum number of breakpoints allowed is max-number as shown in the error message. You must explicitly delete a breakpoint before adding any new ones. Alternatively, you could re-invoke CrossView Pro with the -b option to increase the maximum number of breakpoints.

Too many locals (> max-number)

Eliminate some existing locals or reinvoke CrossView Pro with the -s switch to increase the number of locals allowed.

Too many modules

The symbol file describes an application that was constructed from more than 1818 modules.

Too many processes (> max-number)

CrossView Pro allows only one process to be debugged.

Too many streams (> max-number)

The maximum number of I/O streams, max-number, has been reached. You must eliminate an I/O stream before adding a new one.

Trace size is required

The required format of the command is exp ct, where exp is the number of statements to trace. Re-enter the command with a value for exp.

Type 'r ', to run program from power-on conditions or 'c ' to continue with current program pointer

This is to inform you that command r is not implemented and that you should used r or c.

Type of command-line-expression is too complex

The command line function returns a data type that CrossView Pro cannot handle. An example would be a function returning a structure.

Unexpected breakpoint type 'type'

CrossView Pro has encountered a breakpoint with an unknown type attribute. Verify the previous break commands and re-try. If the condition persists, please contact the TASKING Technical Support staff for assistance.

Unknown command `command' (<number>)

CrossView Pro does not recognize command, and has echoed the command number for Technical Support purposes. Please check the spelling and retry. If the condition persists, please contact the TASKING Technical Support staff for assistance.

Unknown data monitor id 'number'

The monitor number number that you tried to delete does not exist. Use the M command to list currently monitored variables.

Unknown data size

Valid data sizes are 1, 2, 4, or 8 bytes.

Unknown display mode

See chapter Accessing Code and Data, for a list of display mode options.

Unknown name 'name'

Variable name is not in scope or is undefined.

Unknown procedure "name".

The function name does not exist in any file that CrossView Pro knows about. The file containing name may not have been compiled with the -g debug switch.

Unknown macro 'name'

CrossView Pro does not recognize the macro name as given. Please check the spelling. You may list all current macros by using the set command with no arguments, or display the Macro window for currently defined macros.

Unknown window

CrossView Pro does not recognize the window name as given. See chapter Command Reference for valid window arguments.

Unsupported format type (parameter)

Supported types are c (character), x (hex), and o (octal).

Value number is not defined for this enum.

The member specified was not part of the enumerated set. Please check the spelling and verify that the correct enum was used.

Value exceeds depth of stack.

A stack level was specified that does not currently exist. Please check the value and retry. Check the stack window for valid stack levels, or execute a t command (trace stack) to determine the depth of the stack.

VMS error : cannot establish handler for signals

CrossView Pro on VMS could not establish proper error handlers. If the condition persists, please contact the TASKING Technical Support staff for assistance.

VMS error : cannot establish pasteboard

CrossView Pro on VMS can not establish the running environment. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

VMS error : cannot establish virtual keyboard

CrossView Pro on VMS can not establish the running environment. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

VMS error code = number \ Attempt to get message text fail.

CrossView Pro on VMS received an error while attempting to provide an error diagnostic message from the host error message library. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Warning: NULL pointer dereference

The expression contained a null pointer dereference. Check the expression for possible errors, or verify that the pointer should in fact be null.

Warning: pointer dereference with invalid segment selector.

The pointer is addressing invalid memory and the dereference may report unexpected data results. Check the initialization of the pointer or verify that it has been set correctly.

Warning: too few parameters.

The command given was not invoked with the proper number of arguments. CrossView Pro will supply the command with defaults which may or may not produce the result you expected.

Warning: Using file-b instead of file-a

CrossView Pro could not find file-a, or file-a's status was such that CrossView Pro could not use it. If file-b is not correct, check file-a spelling and its directory.

Warning: X=Y: X is x-size bytes and Y is y-size bytes

The assignment of two different size variables may cause unexpected results. Please correct the condition if possible. This condition is common when assigning string variables where string y is shorter than string x.

Warning: X=Y: X is x-size words and Y is y-size words

The assignment of two different size variables may cause unexpected results. Please correct the condition if possible. This condition is common when assigning string variables where string y is shorter than string x.

Warning: CrossView comment terminated by end of command line source-command-line

The playback file has a comment that was not terminated. It is by default terminated, but if the next line was the continuation of the comment, then unexpected results may occur. Please terminate comment strings on each line to avoid this warning.

Windows not enabled; use WW to enable

The command issued can only be used when windows are enabled.

Write I/O request could not be queued

CrossView Pro received a condition that it could not handle. If the condition persists, please contact your system administrator, or call the TASKING Technical Support staff for assistance.

Write-only register. Value may not be valid.

CrossView Pro set a write-only register but has no way of verifying the correctness of the register contents.

Wrong storage class for data breakpoint

You may not set a data breakpoint at the address of a register variable or special variables.

CrossView could not disassemble the emulator's trace buffer because the address information in the buffer is incorrect.

The trace buffer may be corrupted. Re-check the commands leading to this condition, and retry. If the condition persists, please contact the TASKING Technical Support staff for assistance.

XVW error - message
or
XVW Fatal error - message

These messages are generated by internal conditions that should not normally occur. The message is usually encrypted and should be brought to the attention of the TASKING staff. Please contact the TASKING Technical Support staff for assistance.

XVW:main - Cannot continue, incomplete initialization.

CrossView Pro's initialization was interrupted and could not be completed. Please re-start CrossView Pro, and if the condition persists, contact the TASKING Technical Support staff for assistance.

You can't goto a line outside of the current procedure

The specified line number is outside the current procedure. Change the line number to one within the procedure or enter the correct procedure before executing this command.

You may not assign from a host system string/array

The expression given performs an assignment that CrossView Pro can not perform at this time.

You may not assign from a void function

The expression attempts to assign a variable from a void function. Please check the return value of the function and verify that you are referencing the correct function.

You may not assign more than max-size bytes to a special variable

An attempt was made to assign greater than the maximum number of bytes to a special variable. Check the expression for errors, and check the variable's spelling.

You may not assign to a constant

The value of a constant cannot be changed. Check the name that you have specified.

You may not mix assignment of a scalar and an aggregate

An attempt was made to assign incompatible types of data. Please check the data types and retry.

You need to supply a program name.

CrossView Pro requires a program name to debug on the invocation line.


Copyright © 2000 TASKING, Inc.