Symbolic Debugger

ATTEMPT TO READ ON NON-WORD BOUNDARY

The debugger cannot read on a non-word aligned address.

Do not try to read at a non-word boundary. An incorrect reference to a data item has probably been made. Note: Memory accesses are done word-at-a-time, regardless of how data is formatted in memory.

ATTEMPT TO WRITE TO ODD ADDRESS

An attempt to write a value on a non-word or half-word boundary was made.

Do not try to write to an odd address. Note: Memory accesses are done word-at-a-time, regardless of how data is formatted in memory.

ADDRESS NOT FOUND

The address is part of a command and is invalid. It is probably out of range.

Check the validity of the address and re-enter the command.

CANNOT READ THAT LOCATION

Access to the child process failed, possibly caused by an invalid address.

Check the validity of the address and re-enter the command.

NO CHILD PROCESS

The debugger attempted an operation that required a child process that does not exist (was not running).

To start a child process, use any of the run or step commands.

ATTEMPT TO WRITE TO NON-WORD BOUNDARY.

The debugger cannot write to a non-word aligned address.

Do not try to write to a non-word boundary. An incorrect reference to a data item has probably been made. Note: Memory accesses are done word-at-a-time, regardless of how data is formatted in memory.

CANNOT WRITE THAT LOCATION

Access to a child process failed; this may have been caused by an invalid address.

Check the validity of the address and re-enter the command.

BAD ACCESS TO CHILD PROCESS

Failed to read data from or write data to a child process. This may have been caused by an invalid address (for example, dereferencing an invalid pointer), or by an attempt to place a breakpoint in an unwritable child process code space.

Check the validity of the data and re-enter the command.

CAN'T SET BREAKPOINT (INVALID ADDRESS)

The address of the specified breakpoint command was invalid or unknown.

Re-enter the breakpoint command with a correct address.

STACK ISN'T THAT DEEP

The debugger tried to set a breakpoint or view a procedure at an invalid depth. The child process stack was not that deep.

Use the trace command to list the child process stack.

NO SYMBOLS FOR THAT PROCEDURE

The debugger tried to set a breakpoint using a stack depth, when the procedure at that stack depth was non-debuggable.

Try setting a breakpoint-address using the name of the procedure; for example, ba xxx.

INVALID BREAKPOINT TYPE "TEXT"

TEXT was an invalid breakpoint type.

Refer to the "Breakpoint Commands" section in the HP Symbolic Debugger User's Reference Manual to see valid breakpoint commands.

INVALID LINE NUMBER ON "CMD" COMMAND

The quantity given for a line number on a breakpoint, view, or continue command, was an invalid numeric expression.

Re-enter the command with a valid expression.

NO SUCH PROCEDURE OR FILE NAME "TEXT"

An attempt was made to set a breakpoint, or continue to a procedure or file TEXT that did not exist, or was non-debuggable.

Use the lp (list procedures) command to list all known debuggable procedures and use the lf (list files) command to list all known source files.

PROCEDURE "PROC" NOT FOUND WHERE SPECIFIED

The nesting of procedure PROC was not properly specified.

Use the trace command to list the stack.

LABEL "TEXT" NOT FOUND WHERE SPECIFIED

The proc #label was entered incorrectly and that label is not found in the named procedure.

Re-enter the command, giving a valid proc #label combination.

NO COUNT GIVEN FOR "CMD" COMMAND

The user failed to specify a breakpoint count (after the \) for a breakpoint command. Or, an attempt was made to use the breakpoint count command on an existing breakpoint.

Refer to the "Breakpoint Commands" section in the HP Symbolic Debugger User's Reference Manual to see the correct syntax for breakpoint commands.

COUNT MUST BE POSITIVE OR NEGATIVE

A count of zero was given for a breakpoint or breakpoint count command.

Re-enter the command with a non-zero count.

MUST SPECIFY A MACRO NAME

The def command was entered without arguments.

Refer to the "Macro Facility Commands" section in the HP Symbolic Debugger User's Reference Manual to see the correct syntax for the def command.

"NAME" IS NOT A VALID MACRO NAME

The debugger tried to define a macro via the def command where the NAME specified was not a string of alphanumeric characters beginning with a letter.

Re-enter the def command using a string of characters beginning with a letter for the macro name.

MUST SPECIFY WHICH MACRO TO DELETE

The undef command was entered to delete or undefine a macro without giving the name of the macro to delete.

Use the lm (list macros) command to list all defined macros.

UNKNOWN NAME OR COMMAND "NAME"

An unrecognized string (NAME) was encountered as a debugger command.

Refer to the HP Symbolic Debugger/XL Quick Reference Guide to see tables of valid debugger commands.

UNKNOWN COMMAND "CMD" (NUM)

The command CMD (internal value NUM) is not supported. The message "Unknown name or command" is usually displayed.

Refer to the HP Symbolic Debugger/XL Quick Reference Guide to see tables of valid debugger commands.

EMPTY ASSERTION NOT ADDED

The assertion command was given without an associated command list.

Re-enter the command and include a command-list within braces ({ }).

NO BREAKPOINT SET AT CURRENT LOCATION

An attempt was made to activate, delete, or suspend a breakpoint where no breakpoint was defined.

Use the lb (list breakpoints) command to see where breakpoints are set.

ADDRESS IS REQUIRED AFTER "CMD"

The ba (breakpoint address) command must be followed by a code address.

Use a valid code address (symbolic or numeric) with the command.

INVALID DEPTH GIVEN FOR "CMD" COMMAND

An attempt was made to specify a depth that is not a number greater than or equal to 0.

Re-enter the appropriate command with a valid depth.

DEPTH MUST BE AN INTEGER

An attempt was made to specify a stack depth that is not a number.

Re-enter the command and specify an integer depth.

"CMD" NOT ALLOWED WHILE RUNNING ASSERTIONS

These commands cannot be executed while assertions are active: c (continue), C (Continue), r (run), R (Run), s (step), S (Step), or k (kill). If one of these commands appears in an assertion command list, it must follow an x (exit) command with a non-zero modifier.

Exit assertion mode to execute the command or delay using the command.

"da," "db," OR "dp" IS REQUIRED

The d (delete) command has only three valid variations. This d (delete) command was followed by something other than an assertion, breakpoint, or procedure command.

Refer to the HP Symbolic Debugger User's Reference Manual to see valid delete commands.

MUST SPECIFY WHICH ASSERTION TO SUSPEND

MUST SPECIFY WHICH ASSERTION TO DELETE

The number of the assertion to suspend or delete was not specified.

Use the la (list assertions) command to find the number of the assertion to suspend or delete.

"Directory" COMMAND NEEDS A DIRECTORY NAME (IN QUOTES)

The D (Directory) command was invoked without specifying a directory name surrounded by double quotation marks ( " ).

Re-enter the D (Directory) command and enclose a valid directory name in quotation marks ( " ).

INVALID EXPRESSION FOR DEPTH ON "CMD" COMMAND

The CMD command was given with an expression for a depth that the debugger cannot evaluate.

Use the t (trace) command to view the stack for the proper procedure and depth.

"format" COMMAND NEEDS A STRING ARGUMENT

The f (format) command was followed by something other than null or a string in quotation marks.

Refer to the "Miscellaneous Commands" section in the HP Symbolic Debugger User's Reference Manual for more information about the f (format) command.

"goto" MUST BE FOLLOWED BY A LINE NUMBER

A g (goto) command was given without a numeric argument or valid label.

Refer to the "Miscellaneous Commands" section in the HP Symbolic Debugger User's Reference Manual for more information about the g (goto) command.

MISSING "{"

The i (if) command did not have a brace ( { ) following the conditional expression. Or, the expression might have been entered incorrectly.

Re-enter the expression, enclosing the command-lists in braces.

MAP IS NOT SUPPORTED

Your version of the debugger does not support the M (Map) command, because core files are unsupported.

Do not enter the M (Map) command.

INVALID EXPRESSION GIVEN FOR "CMD" COMMAND

A non-numeric expression was entered as part of the s (step), S (Step), t (trace), T (Trace), and sa (suspend assertion) commands.

Re-enter the command with a correct numeric expression.

"t" MUST BE FOLLOWED BY "a", "b", "c", "m", or "r", OR EXPRESSION

As part of the t (toggle) command, the t (toggle) was not followed by one of these commands: a (assertion), b (breakpoint), c (case), m (macros), or r (recording).

Refer to the individual command listings in the HP Symbolic Debugger User's Reference Manual to see valid toggle commands.

INVALID WINDOW SIZE

The numeric expression given for the new window size on the window command was not a valid numeric expression or was outside the range of 1 to 21.

Re-enter the command with a valid numeric expression within the range of 1 to 21.

"exit" IS ONLY ALLOWED WHILE RUNNING ASSERTIONS

The debugger tried to exit the assertions mode while assertions were not active.

Refer to the x (exit) command listing in the HP Symbolic Debugger User's Reference Manual.

NO PLAYBACK NAME SPECIFIED

The < or << command was given without a file name argument.

Re-enter the command with the playback file name.

CAN'T OPEN "FILE" AS PLAYBACK FILE

The system failed to open the specified playback file.

Check the file path and permissions.

CAN'T OPEN "FILE" AS RECORD FILE

The system failed to open the specified record file.

Check the file path and permissions.

OPERATOR STACK OVERFLOW

The expression was too complicated for the expression handler to parse. A combination of more than 15 nested parentheses and/or pending operators may be the cause.

Re-enter the expression, using less than 15 nested parentheses.

OPERATOR STACK UNDERFLOW

The expression handler failed. This may have been caused by a corrupt environment or a parsing problem.

Re-enter the expression in an alternate form, if possible.

DATA TOO BIG TO PUT IN THE CHILD PROCESS

A string constant or other data was larger than the total size of the buffer in xdbend.lib.sys

Re-enter a smaller string constant or data item, if applicable.

CAN'T STORE INTO A CONSTANT

The left side of an assignment statement was found to be a constant; it cannot be modified.

Use the \t display format for information on the assigned variable.

CAN'T SET ANY REGISTERS

Setting registers incorrectly is inherently dangerous and can lead to complete lockup of the operating system.

Only use the g (goto) command to make limited, safe changes to the program counter ($pc). Avoid changing register values directly.

STRING TOO LONG FOR ASSIGNMENT

An attempt was made to assign a string over 1024 bytes to an HP FORTRAN 77 CHAR*, HP Pascal string, or HP Pascal packed array of char.

Use the \t display format for type information of the string assigning to, and re-enter the command with an appropriately sized string.

INCOMPATIBLE OPERANDS FOR STRING ASSIGNMENT

An attempt was made to assign to an HP FORTRAN 77 CHAR*, HP Pascal string, or HP Pascal packed array of char, something other than an HP FORTRAN 77 CHAR*, HP Pascal string, HP Pascal packed array of char, a string constant, or a character constant.

Re-enter the command with a proper assignment.

CAN'T DEREFERENCE A CONSTANT

An attempt was made to dereference a constant.

Use the \t format to find the type of the object to be displayed.

CAN'T TAKE THE ADDRESS OF A CONSTANT

CAN'T TAKE THE ADDRESS OF A REGISTER

Operand of &, $addr, or addr operator is marked as a constant or register type.

Use the \t display format to find the type of the object being displayed.

POSTFIX "++" NOT SUPPORTED

POSTFIX "--" NOT SUPPORTED

PREFIX "++" NOT SUPPORTED

PREFIX "--" NOT SUPPORTED

An attempt was made to use an unsupported operator. For example, ++n, --n, n++, n--.

Make sure a space is used between a + or - operator and a unary sign (for example 2- -5). +=1 or -=1 can be used to increment or decrement, respectively.

INVALID COMBINATION OF OPERATOR AND OPERANDS

The debugger tried to perform a numeric operation on one or more non-numeric operands.

Re-enter the command with a valid expression.

UNKNOWN OPERATOR (NUM)

An unsupported operator, with internal value NUM, was pushed on the operator stack.

Re-enter the command using an operator known to the current language or reset $lang to the language in which the operator is valid.

MISFORMED EXPRESSION

An expression was entered incorrectly. The debugger attempts to show you where the error was detected in the command line. The error token might be one token beyond the actual error.

Re-enter the expression using operators and operands known to the current language or reset $lang to the language in which the operator or operand is valid.

TWO OPERATORS IN A ROW

The expression handler detected an improper construct in an expression.

Re-enter the command with a valid expression.

FORTRAN VARIABLE NOT PURE ARRAY

An attempt was made to dereference an array that had pointer or function qualifiers, while the current language was set to FORTRAN, which does not support them.

Try again with $lang set to a different language.

INVALID REAL NUMBER

The specified numeric expression was not a real number.

See the appropriate language reference manual, or Table 4-3 in this manual, for the format of real numbers.

MISFORMED GLOBAL NAME

Colon ( : ) must be followed by a variable name (string).

Refer to the "Entering Variable Names" section in the HP Symbolic Debugger User's Reference Manual to see how to specify global variables.

UNKNOWN GLOBAL

The variable specified with :var was not a recognized global variable name.

Use the lg (list globals) command to list all known global variables.

NEED A ":" AFTER THE NUMBER

Proc:depth:var was entered incompletely (:var was missing).

Refer to the l (list) command listing in the HP Symbolic Debugger User's Reference Manual to see a list of variables.

INVALID LOCAL NAME

Proc[:depth]:var was entered incorrectly. Var must be a valid variable name in the specified procedure, at the specified depth.

UNKNOWN LOCAL

The variable specified with proc[:depth]:var was not a recognized local variable of proc.

Use the l (list) command to list all known local variables of the current proc, or use the T (Trace) command to list the locals, variables, and procedures on the stack.

PROCEDURE "PROC" NOT FOUND AT STACK DEPTH NUM

In proc:depth, the procedure PROC was not on the child process stack at depth NUM. Either the stack was not that deep, or the procedure at that depth was not PROC.

Use the t (trace) command to list the stack.

UNKNOWN LANGUAGE

An attempt was made to modify the current language by assigning an invalid language designator to the special variable $lang. The valid language designators are COBOL, Pascal, FORTRAN, C, and default.

Re-enter the command with COBOL, Pascal, FORTRAN, C, or default as the designator.

LOCAL IS NOT ACTIVE

A local variable name was recognized but the procedure it belongs to was not currently active on the child process stack.

Re-enter the command after its procedure has been called.

TWO OPERANDS IN A ROW

The expression handler detected an improper construct in an expression.

Refer to the "Entering Expressions" section in the HP Symbolic Debugger User's Reference Manual (31508-90003).

NO SOURCE FILE FOR CURRENT ADDRESS

The given child process address did not map to a known, debuggable source file.

Use the lf (list files) command to view the files the debugger recognizes, and re-enter the command with an appropriate address expression.

NO SEARCH PATTERN

The search command (/, ?, n (next), or N (Next)) was given without a search pattern (in the case of n (next) and N (Next), the previous search command / or ? was provided without a pattern).

Refer to the individual command listings in the HP Symbolic Debugger User's Reference Manual for more information about search commands.

NO MATCH FOR "TEXT"

The search pattern (TEXT) for the /, ?, n, (next) or N (Next) command was not found in the current viewing file. Note that the pattern is a literal, not a regular expression.

Try another pattern or view another file and search for the pattern.

INVALID DISPLAY FORMAT "TEXT"

Given the data display format, or a portion of it, the TEXT contained invalid syntax.

Refer to Table 4-3 in the HP Symbolic Debugger User's Reference Manual to see valid data viewing formats.

LENGTH NOT ALLOWED WITH "TEXT" FORMAT

Given the data display format, the TEXT did not allow the data length specification because it is irrelevant or implicit in the format.

Refer to the HP Symbolic Debugger User's Reference Manual to see valid data viewing formats.

THIS DOES NOT APPEAR TO BE A STRUCT OR UNION

THIS DOES NOT APPEAR TO BE A RECORD OR UNION

The debugger tried and failed to dump the contents of a data object that was not a struct, union, or record.

Use the \t display format for more information.

NO CURRENT PROCEDURE

The debugger tried to list locals for the current viewing procedure when the procedure was undefined.

Use the lp (list procedures) command to list all the debuggable procedures.

NO SUCH PROCEDURE "PROC"

An attempt to list locals of a non-existent, or non-debuggable procedure PROC was made.

Use the lp (list procedures) command to list all known debuggable procedures.

UNRECOGNIZED "l" COMMAND

The l (list) command was given with a second part that was neither a known procedure name, nor a valid option.

Refer to the l (list) command listing in the HP Symbolic Debugger User's Reference Manual for more information.

":" MUST BE FOLLOWED BY A DEPTH

Proc:depth was entered incorrectly.

Refer to the individual command listings in the HP Symbolic Debugger User's Reference Manual for more information.

EXITING COMMAND LINE PROCEDURE CALL

The command line procedure call environment terminated for an unusual reason, such as a break was encountered during program execution, or an error was reached before the procedure was called.

Check the procedure call for errors and re-enter the command line procedure call.

CAN'T PASS MORE THAN NUM ARGUMENTS TO CALLED PROCEDURE

A large limit (NUM) exists on how many parameters can be passed to a procedure called from the command line.

Check the number of parameters for the procedure you are attemping to call. If the limit (NUM) is less than the number of parameters in the procedure, that procedure cannot be called from the command line.

ARGUMENT LIST TOO LONG

Arguments to the run command exceeded 1024 bytes.

Re-enter the run command with fewer arguments.

CAN'T GOTO A LINE OUTSIDE OF THE CURRENT PROCEDURE

The line number given to the g (goto) command was not an executable source line in the top procedure or paragraph on the child process stack. This is not always the same as the current viewing procedure.

Re-enter the g (goto) command with a line number within the procedure or paragraph on the top of the child process stack.

UNKNOWN NAME

An unrecognized string (procedure or variable name) was encountered in an expression.

Use the lp (list procedures), lg (list globals), l (list), lc (list commons), or ll (list labels) command to list all known procedures, globals, locals, commons, or labels.

MISFORMED HEX NUMBER

0x or 0X was given without digits following.

Re-enter the command with a valid hexadecimal number.

MISFORMED OCTAL NUMBER

An octal number starting with 0 contains an 8 or 9.

Re-enter the command with the correct octal number.

CHARACTER CONSTANT IS MISSING ENDING

Token parsed as a character constant is missing a trailing single quotation mark ('). This applies to a single quotation mark followed by a single character or equivalent, backslash sequence.

Re-enter the command enclosing the character constant in single quotation marks (').

STRING CONSTANT IS MISSING ENDING "

Token parsed as a string constant was missing a trailing double quotation mark before the end of the command line.

Re-enter the string with a beginning and ending double quotation marks.

MACROS NESTED TOO DEEPLY

A user specified macro has caused the evaluation of over 20 macro definitions during its evaluation. The debugger cannot evaluate macros nested this deep. This error can also be caused by a recursive macro definition.

Redefine the macro using fewer than 20 macro definitions, or remove the recursive definition.

MACROS PROCESSING OVERFLOW

While evaluating a userh specified macro, the buffer used to hold the resulting definition for this macro was about to overflow, and the processing for this macro terminated unsuccessfully.

Undefine the unnecessary macros and redefine the macro.

SORRY, YOU CAN'T ACCESS A NAKED FIELD

An attempt was made to refer to a field by name without specifying the qualifying structure (for example, union, record, pointer, etc.).

Use the \t display format for more information.

TOO MANY SUBSCRIPTS

An attempt was made to dereference an array with more dimensions than it was declared to have. However, HP C does allow you to dereference pointers in this manner.

Use the \t display format for more information.

INVALID FIELD ACCESS: "NAME"

An attempt was made to do a field dereference of an object (NAME) that was not a structure or union.

Use the \t display format to determine the characteristics of the object (NAME).

NO SUCH FIELD NAME "NAME" FOR THAT RECORD

NO SUCH FIELD NAME "NAME" FOR THAT STRUCT

NO SUCH FIELD NAME "NAME" FOR THAT UNION

Struct (union, record) did not contain a field of that NAME.

Use the \t display format for more information.

OPERAND STACK OVERFLOW

An expression was too complicated for the expression handler to parse. A combination of more than 15 nested parentheses and/or pending operators may be the cause.

Re-enter the expression, using less than 15 nested parentheses.

CAN'T EXECUTE CHILD PROGRAM

The debugger could not execute the object file given.

Check to see that the file is executable.

WINDOW MODE REQUIRED FOR THIS COMMAND

The debugger was probably invoked with the -L option.

Verify that you are using an HP terminal and rerun the debugger without the -L option.

NO SUCH FIELD: "NAME"

The simple field NAME or field list specified does not exist.

Check the declaration for the correct field name or field list.

NON-UNIQUE FIELD LIST

The field name or field list specified does not uniquely identify a single field.

Use a more complex field list to ensure it identifies a single field.

CAN'T MIX . AND OF OPERATORS

The field list includes both the . and of operators.

Use only the . or of operator.

ONE ARRAY SUBSCRIPT EXPECTED

The field specified is a table or one of the field's ancestors is a table, but no array subscript was given.

Determine which field is a table, and use the appropriate subscript.

LIST OF <NUMBER> ARRAY SUBSCRIPTS EXPECTED

The field specified is a table and/or one or more of the field's ancestors is a table; <number> subscripts are required, but no array subscripts were given.

Determine which fields are tables, and use the appropriate < number> of subscripts.

NOT ENOUGH ARRAY SUBSCRIPTS, EXPECTED <NUMBER>

There are more tables among the field and its ancestors than there were subscripts given.

Determine which fields are tables, and supply < number> subscripts.

UNEXPECTED ARRAY SUBSCRIPT LIST

Neither the field specified nor any of its ancestors are tables, but one or more subscripts was given.

Do not give a list of subscripts.

CAN'T MOVE TO A CONSTANT

The item which is the destination of the move is a constant.

Do not attempt to store into a constant, or look at the declarations to determine the correct field name.

CAN'T MOVE TO THAT DESTINATION

The item which is the destination of the move is of a type into which the debugger can not store.

Do not attempt to store into that item, or look at the declarations to determine the correct field name.

CAN'T HANDLE EDITED FIELDS AS DESTINATION

The item which is the destination of the move is an edited field.

None, the debugger can not currently handle edited fields as the source or destination of a mov (move) command.

CAN'T HANDLE EDITED FIELDS AS SOURCE

The item which is the source of the move is an edited field.

None, the debugger can not currently handle edited fields as the source or destination of a mov (move) command.

CAN'T MOVE NUMERIC FIELD TO ALPHABETIC FIELD

The source of the move is a numeric field, while the destination field is alphabetic.

None, moving a numeric field to an alphabetic field is illegal.

CAN'T MOVE NUMERIC FIELD WITH A FRACTION TO ALPHANUMERIC FIELD

The source of the move is a numeric field which has a fraction, while the destination field is alphanumeric.

None, moving a numeric field with a fraction to an alphanumeric field is illegal.

CAN'T MOVE ALPHABETIC FIELD TO NUMERIC FIELD

The source of the move is an alphabetic field, while the destination field is numeric.

None, moving an alphabetic field to a numeric field is illegal.

CAN'T MOVE ALPHANUMERIC FIELD CONTAINING NON-DIGIT TO NUMERIC FIELD

The source of the move is an alphanumeric field containing a non-digit, while the destination is numeric.

None, moving an alphanumeric field containing a non-digit to a numeric field is illegal.

INVALID SIGN IN PACKED DECIMAL NUMBER

The packed decimal field that is either being displayed or being used as the source of a move contains an invalid sign field.

Use either a data field that redefines the packed decimal field, or use the group field that contains the packed decimal data field.

INVALID DIGIT IN PACKED DECIMAL NUMBER

The packed decimal field that is either being displayed or being used as the source of a move contains an invalid digit.

Use either a data field that redefines the packed decimal field, or use the group field that contains the packed decimal data field.

INVALID SIGN OVERPUNCH IN DISPLAY NUMBER

The display field that is either being displayed or being used as the source of a move contains an invalid sign overpunch.

Use either a data field that redefines the display field, or use the group field that contains the display field.

INVALID SEPARATE SIGN IN DISPLAY NUMBER

The display field that is either being displayed or being used as the source of a move contains an invalid separate sign.

Use either a data field that redefines the display field, or use the group field that contains the display data field.

TOO MANY ARRAY SUBSCRIPTS, EXPECTED <NUMBER>

There are less tables among the field and its ancestors than there were subscripts.

Determine which fields are tables, and supply < number> subscripts.

SUBSCRIPT NUMBER <SUBSCRIPT> OUTSIDE RANGE <LOW> TO <HIGH>.

Subscript number <subscript> was outside the valid range of <low> to < high>.

Supply a value between <low> and <high>.

Assigning to NUM byte object from NUM byte object; moved NUM bytes

The object on the left side of an assignment was not equal to the size of the right side of the expression. The debugger copied a series of bytes equal in size to the left side of the assignment statement.

Re-enter the command, using expressions of equal length, or else results based on truncation will occur.

WARNING: "FILE" DOES NOT APPEAR TO HAVE LINE SYMBOLS

When opening the source file (FILE) associated with a procedure, no entries in the source line table were found for the procedure. The procedure may not have any executable lines, or the object file may have been corrupted.

Recompile the program with the symbolic debugger option.

WARNING: "FILE1" IS YOUNGER THAN "FILE2"

The source file (FILE1) modification time is newer than the object file (FILE2) modification time, so the source file may not correspond to the code in object file.

Recompile the source file with the symbolic debugger option to update the object file.

WARNING: CODE IS SHARED; YOU CAN'T SET BREAKPOINTS SO YOU CAN'T RUN.

The object file was set to a shared mode that prevented the debugger from writing breakpoints into a child process code in memory. Because an initial breakpoint is required when starting a child process, you cannot do any useful debugging without one. If you try to start a child process, you may receive the message: "Bad access."

If possible, modify the object file to no longer be in shared mode.

WARNING: "XDBEND" WAS NOT LINKED WITH THIS PROGRAM

The special procedure "_end_" was not found in the symbol table during initialization. If xdbend is missing, string constants and some other values cannot be stored in the child process address space when required, resulting in an error at that time.

Re-link the program with xdbend.lib.sys.

WARNING: TOO FEW PARAMETERS

An attempt was made to call a debuggable procedure from the command line with a different number of parameters than specified in the symbol table. The procedure can still be called, but it may lead to odd results which depend on the language and the called procedure.

Use the V (View) command to view the procedure to determine the correct number of parameters.

WARNING: TOO MANY PARAMETERS

An attempt was made to call a debuggable procedure from the command line with a different number of parameters than specified in the symbol table. The procedure can still be called, but it may lead to odd results which depend on the language and the called procedure.

Use the V (View) command to view the procedure to determine the correct number of parameters.