HP 3000 Manuals HP 3000 Manuals
Chapter 5 DEBUG ERROR MESSAGES
When an error is detected by DEBUG, it issues a message in the form:
message n
where:
message indicates the type of error.
n indicates the character position in the command where
the error was detected.
For example, suppose you enter the following command:
?DQ+ 1:,8,A\over SYNTAX 6 message issued by DEBUG
This indicates that there is a syntax error following character position
6.
In this case, it is the decimal value 8 that is in error. To correct,
re-enter the command:
?DQ+ 1:,#8,A
The five possible messages issued by DEBUG are defined in Table 5-1.
Table 5-1. DEBUG Error Messages
------------------------------------------------------------------------------------------------
| | | |
| MESSAGE | MEANING | CORRECTIVE ACTION |
| | | |
------------------------------------------------------------------------------------------------
| | | |
| BOUNDS | A specified location is outside the | Check your command to make sure it |
| | permitted bounds. For example, in | is entered correctly. If it is, |
| | non-privileged mode, you referenced a | lower or raise the referenced |
| | location above S or below DL in the | location. Note that using an |
| | data stack; or, in privileged mode, | indirect address where you want |
| | you referenced code outside the | direct can produce a bounds |
| | specified segment, or an absolute | violation. |
| | address outside memory. | |
| | | |
------------------------------------------------------------------------------------------------
| | | |
| CHECK | New breakpoint conflicts with | This is a warning only. You may |
| | established breakpoint. This usually | continue. Any new breakpoints will |
| | occurs when you specify as new a | be established, existing breakpoints |
| | breakpoint that already exists. | are not affected. If you wish, |
| | | check all existing breakpoints with |
| | | the B@ command. |
| | | |
------------------------------------------------------------------------------------------------
| | | |
| FULL | The breakpoint table established at | Probably too many users are |
| | system configurations full. | currently using DEBUG. Wait and try |
| | | again. If this message happens |
| | | consistently, request your system |
| | | manager to re-configure with a |
| | | larger breakpoint table. |
| | | |
------------------------------------------------------------------------------------------------
| | | |
| NO-NO | Invalid information was provided in a | Check the information provided in |
| | command whose syntax is correct. For | your command. For instance, if you |
| | instance, you specified a logical | entered B 5.166+70, make sure that |
| | segment number that does not exist. | you actually have six segments in |
| | | your code. Correct and continue. |
| | | |
------------------------------------------------------------------------------------------------
| | | |
| SYNTAX | The command syntax is in error. | Check the syntax and continue. |
| | | |
------------------------------------------------------------------------------------------------