PX(1) PX(1) NAME px - Pascal interpreter SYNOPSIS px [ obj [ argument ... ] ] DESCRIPTION _P_x interprets the abstract machine code generated by _p_i_. The first argument is the file to be interpreted, and defaults to _o_b_j; remaining arguments are available to the Pascal program using the built-ins _a_r_g_v and _a_r_g_c_. _P_x is also invoked by _p_i_x 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. The p option of _p_i suppresses all of this except the message indicating the cause of abnormal termination. FILES obj default object file pmon.out profile data file SEE ALSO Berkeley Pascal User’s Manual pi(1), pix(1) DIAGNOSTICS Most run-time error messages are self-explanatory. Some of the more unusual ones are: Reference to an inactive file A file other than _i_n_p_u_t or _o_u_t_p_u_t was used before a call to _r_e_s_e_t or _r_e_w_r_i_t_e_. Statement count limit exceeded The limit of 500,000 executed statements (which prevents exces‐ sive looping or recursion) has been exceeded. 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: _S_o_m_e _m_e_s_s_a_g_e Indicates an internal inconsistency detected in _p_x probably due to a Pascal system bug. AUTHORS Charles B. Haley, William Joy, and Ken Thompson VAX-11 version by Kirk McKusick BUGS Post-mortem traceback is not limited; infinite recursion leads to almost infinite traceback. 3rd Berkeley Distribution May 12, 1986 PX(1)