Error messages are preceded by:
Error:
The messages are:
Address not specified
Possible cause: You have used thearray command, but have not specified any address.
Action: Specify the address whose contents you want to print (for more details, see array, on page 80.
Attempt to select non-existent stack frame
Possible cause: You have used one of the stack navigation commands up ordown,when the current procedure was at the top or bottom of the stack respectively.
Action: Usethebacktrackcommand to check the position of the current procedure on the stack.
Cannot open process log file
Possible cause: The program cannot create the dumptile DOF-file-name. dr or dapcore.
Action: Change the permissions on the directory if necessary (using chrnod nnn log-file-name).
Column specified out of range
Possible cause: In thearraycommand, youspecified the columns parameter incorrectly (for more details, see array, on page 80).
Action: Make sure that any column limits you specify are in the range 0 to (ES—i) where ES is the DAP edge-size.
DAP Series: Program Development under UNIX manOO3.04 753
Count too large
Possible cause: You specified a count field for thearraycommand that wastoolarge.
Action: Reduce the size of the count field.
Data section or area name not recognised
Possible cause: The name you gave to the array command for a data section or area is unknown.
Action: Check the spelling of the data section name, and the consolidation map (use the —m option to dapf or dapa).
File does not contain requested dim
Possible cause: The dump number you gave to the select command is greater than the largest dump in the dump file.
Action: Select a different dump or possibly a different file.
File is not a process log file
Possible cause: The file you specified in the core command or as a parameter to dapdbis not a process log file.
Action: Check the spellingofthe filename you gave.
First row or column larger than last row or column
Possible cause: A column limit you specified for the firstco!orIastco! parameter for the vertical format option of the the array command is out of range (for further details, see array, on page 80.
Action: Specify a correct limit. Note: the first column specified must be less than or equal to the last column specified.
Illegal character
Possible cause: There is an illegal characterin the array command.
Action: Retype the complete array command line.
Illegal modifier
Possible cause: The syntax for a modifier is incorrect.
Action: The syntax is (mn), where n is in the range 1 to 7; that is, is one of (ml) to fm7).
754 manOQ3.04 AMT
D. 1: Error messages 155
Incompatible PAL trace parameters
Possible cause: The parameters you specifed to thearraycommand ate invalid.
Action: Look at the entry for the array command, on page 80.
Integer or real precision specified is too large
Possible cause: You specifed incorrectly the size field to the array command.
Action: Specify the field correctly. Note: the size field has to be between 1 and 64 for integers, and either 24, 32, 40, 48, 56 or 64 for reals.
Item repeat count too large
Possible cause: You specifed toolarge a *count fieldinthe array command.
Action: Reduce the size of the *countfield
Item repeat count too small
Possible cause: You specified a negative *countfield inthe array command.
Action: Make the *count field greater than 0.
Missing modifier
Possible cause: When you specified a modifier to the address field in the array command, you did not specify a modifier register.
Action: Repeat the array command, and either remove the (mn) altogether, or insert a correctmodifierregister.
Missing start-bit
Possible cause: You specified an array command with rowpack format, but you specified a /start-bft field without specifying a value for start bit
Action: Insert a value after the
I.
Missing count
Possible cause: You specified an array command with a*count field, but did not specify a value for count
Action: Insert a value after the .
DAP Series: Program Development under UNIX manOQ3.04 155
Missing offset
Possible cause: You have specified an offset to the address field in the array command, but either you gave no offset value, or you gave an incorrect value.
Action: Insert a suitable value for the offset (for more details, see array, on page 80.
Name missing from command
Possible cause: You have omitted an obligatory parameter in a call to a command (for example, you issued the the macro command, but gave nonameafter it).
Action: Check the command syntax (for more details, see section 4.7, on page 80.)
No FORTRAN-PLUS procedure selected
Possible cause: You have issuedthe printcommand, but aFORTRAN-PLUS procedure has not beenselected.
Action: Use thebacktrackcommandtocheckwhatthe selected procedure is, then selectthe desired FORTRAN-PLUS routine withthe procedure command or with the stack navigationcommands(up, down, top)
No active procedure selected
Possible cause: You have issued a stack navigation command (up, down, top), but there is no current active procedure.
Action: Select an active procedure using the procedure command or one of the stack navigation commands (up, down, top).
No dump selected
Possible cause: The dump file is corrupt.
Action: Rerun the program and retake dumps as required.
No process log file selected
Possible cause: You haveissueda command todapdbbefore you have selected a dump file.
Action: Use the corecommand to select a file.
Number missing from command
Possible cause: You have specified the select command, but have not specified the dump number required.
Action: Always specify the dump number.
156 manOO3.04 AMT
D. 7: Error messages 757
Number not recognised
Possible cause: You have used an illegal character where a number was expected (for example, select 5s).
Action: Numbers have to be positive integers (hex numbers start Ox, octal numbers start 0, all others are decimal).
Precision for data format used illegal
Possible cause: You have specified the size field incorrectly to the array command.
Action: The size field has to be between 1 and 64 for integers: one of 24, 32, 40, 48, 56 or 64 for reals: 8 to ES (and a multiple of 8) for characters: and 1 to ES for hex and bit format.
Procedure name not recognised
Possible cause: You have give an unknown procedure name as a parameter to the procedure command — or have entered a non-command name on the command line when a non-FORTRAN-PLUS procedure is selected.
Action: Use the backtrack command to find out the active procedures, or look at the map you get with the —m3 option to dapf or dapa to find the names of procedures in the program.
Row specified out of range
Possible cause: You specified incorrect row limit(s) (firstrowor Iastrow) for the vertical format for the array command (for more details, see array, on page 80).
Action: Specify row limits in the range 0 to (ES-i).
Bther ci:
Separator needed, or
Startbit only available in rowpack format
Possible cause: You specified /start-bit for the array command, but did not specify rowpack format.
Action: Select rowpack format fusing r)—for mote details, see array, on page 80.
Stack top pointer fM6) invalid, or
Possible cause: The stack has been corrupted—which is normally because you tried to take a dump before control has passed to the DAP, or because in APAL you had used non-standard DAP-calling conventions.
Action: Make sure you only take dumps after a call toDAPENT or (if you are using APAL) use the standard calling conventions (for more details, see [2], DAP Series: APAL Language, section 9.2)
DAP Series: Program Development under UNIX manOO3.04 757
Startbit too large, last bit exceeds row
Possible cause: You have specified an array command in which the sum ofstart-bitand the sizeof the data item you want to print is greater than DAP edge-size.
Action: Reducestart-bit orthe size of the data item.
Btherd:
System stack base pointer invalid, or
System stack top pointer (LNB) invalid
Possible cause: The stack has been corrupted—which is normally because you tried to take a dump before control has passed to the DAP, or because in APAL you had used non-standard DAP-calling conventions.
Action: Make sure you only take dumps after a call to DAPENT or (if you are using APAL) use the standard calling conventions (for more details, see [2], DAP Series: APAL Language,section 9.2).
Too many address components
Possible cause: You specified addressfor the arraycommand incorrectly.
Action: Specify the array command correctly (for more details, see array, on page 80.
D.2 Internal error messages
Internal error messages are those messages which indicate that an inconsistency has been detected in the debugger’s tables. All such messages are preceded by
Internal error:
Anyof:
Illegal type specified, or
Illegal size specified, or
Message number out of range
Possible cause: You should not see any of these messages.
Action: Contact your AMT representative.