Debugger Errors (DB1-DB8)

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.