interprets the abstract machine code generated by
The first argument is the file to be interpreted, and defaults
remaining arguments are available to the Pascal program using the
when running ``load and go''.
If the program terminates abnormally an error message and a
control flow backtrace are printed.
The number of statements executed and total execution time
are printed after normal termination.
suppresses all of this except the message indicating the cause
pmon.out profile data file
UNIX Pascal User's Manual
Most run-time error messages are self-explanatory.
Some of the more unusual ones are:
Reference to an inactive file
was used before a call to
Statement count limit exceeded
The limit of 500,000 executed statements
(which prevents excessive looping or recursion)
Bad data found on integer read
Bad data found on real read
Usually, non-numeric input was found for a number.
For reals, Pascal requires digits before and after the decimal
point so that numbers like `.1' or `21.' evoke the second diagnostic.
panic: \fISome message\fP
Indicates a internal inconsistency detected in
probably due to a Pascal system bug.
Charles B. Haley, William N. Joy, and Ken Thompson
Post-mortem traceback is not limited;
infinite recursion leads to almost infinite traceback.
Because interrupts sometimes find the system in the middle of a
the error backtrace on an interrupt is occasionally meaningless.
The current line is, however, always correct;
only the call backtrace and the name of the current routine may be lost.