4.3BSD-Reno/share/man/cat1/error.0
ERROR(1) UNIX Reference Manual ERROR(1)
NNAAMMEE
eerrrroorr - analyze and disperse compiler error messages
SSYYNNOOPPSSIISS
eerrrroorr [--nn] [--ss] [--qq] [--vv] [--tt _s_u_f_f_i_x_l_i_s_t] [--II _i_g_n_o_r_e_f_i_l_e] [name]
DDEESSCCRRIIPPTTIIOONN
EErrrroorr analyzes and optionally disperses the diagnostic error messages
produced by a number of compilers and language processors to the source
file and line where the errors occurred. It can replace the painful,
traditional methods of scribbling abbreviations of errors on paper, and
permits error messages and source code to be viewed simultaneously
without machinations of multiple windows in a screen editor.
Options are:
--nn Do _n_o_t touch any files; all error messages are sent to the standard
output.
--qq The user is _q_u_e_r_i_e_d whether s/he wants to touch the file. A ``y''
or ``n'' to the question is necessary to continue. Absence of the
--qq option implies that all referenced files (except those referring
to discarded error messages) are to be touched.
--vv After all files have been touched, overlay the visual editor vi(1)
with it set up to edit all files touched, and positioned in the
first touched file at the first error. If vi(1) can't be found,
try ex(1) or ed(1) from standard places.
--tt Take the following argument as a suffix list. Files whose suffixes
do not appear in the suffix list are not touched. The suffix list
is dot separated, and ``*'' wildcards work. Thus the suffix list:
.c.y.foo*.h
allows eerrrroorr to touch files ending with ``.c'', ``.y'', ``.foo*''
and ``.y''.
--ss Print out _s_t_a_t_i_s_t_i_c_s regarding the error categorization. Not too
useful.
EErrrroorr looks at the error messages, either from the specified file _n_a_m_e or
from the standard input, and attempts to determine which language proces-
sor produced each error message, determines the source file and line
number to which the error message refers, determines if the error message
is to be ignored or not, and inserts the (possibly slightly modified) er-
ror message into the source file as a comment on the line preceding to
which the line the error message refers. Error messages which can't be
categorized by language processor or content are not inserted into any
file, but are sent to the standard output. EErrrroorr touches source files
only after all input has been read.
EErrrroorr is intended to be run with its standard input connected via a pipe
to the error message source. Some language processors put error messages
on their standard error file; others put their messages on the standard
output. Hence, both error sources should be piped together into eerrrroorr.
For example, when using the csh(1) syntax,
make -s lint | error -q -v
will analyze all the error messages produced by whatever programs make(1)
runs when making lint.
EErrrroorr knows about the error messages produced by: make(1), cc(1), cpp(1),
ccom(1), as(1), ld(1), lint(1), pi(1), pc(1), f77(1), and _D_E_C _W_e_s_t_e_r_n
_R_e_s_e_a_r_c_h _M_o_d_u_l_a-_2. EErrrroorr knows a standard format for error messages pro-
duced by the language processors, so is sensitive to changes in these
formats. For all languages except _P_a_s_c_a_l, error messages are restricted
to be on one line. Some error messages refer to more than one line in
more than one files; eerrrroorr will duplicate the error message and insert it
at all of the places referenced.
EErrrroorr will do one of six things with error messages.
_s_y_n_c_h_r_o_n_i_z_e
Some language processors produce short errors describing which
file it is processing. EErrrroorr uses these to determine the file
name for languages that don't include the file name in each er-
ror message. These synchronization messages are consumed en-
tirely by eerrrroorr.
_d_i_s_c_a_r_d Error messages from lint(1) that refer to one of the two
lint(1) libraries, /_u_s_r/_l_i_b_d_a_t_a/_l_i_n_t/_l_l_i_b-_l_c and
/_u_s_r/_l_i_b_d_a_t_a/_l_i_n_t/_l_l_i_b-_p_o_r_t are discarded, to prevent accident-
ly touching these libraries. Again, these error messages are
consumed entirely by eerrrroorr.
_n_u_l_l_i_f_y Error messages from lint(1) can be nullified if they refer to a
specific function, which is known to generate diagnostics which
are not interesting. Nullified error messages are not inserted
into the source file, but are written to the standard output.
The names of functions to ignore are taken from either the file
named ._e_r_r_o_r_r_c in the users's home directory, or from the file
named by the --II option. If the file does not exist, no error
messages are nullified. If the file does exist, there must be
one function name per line.
_n_o_t _f_i_l_e _s_p_e_c_i_f_i_c
Error messages that can't be intuited are grouped together, and
written to the standard output before any files are touched.
They will not be inserted into any source file.
_f_i_l_e _s_p_e_c_i_f_i_c
Error message that refer to a specific file, but to no specific
line, are written to the standard output when that file is
touched.
_t_r_u_e _e_r_r_o_r_s
Error messages that can be intuited are candidates for inser-
tion into the file to which they refer.
Only true error messages are candidates for inserting into the file they
refer to. Other error messages are consumed entirely by eerrrroorr or are
written to the standard output. EErrrroorr inserts the error messages into
the source file on the line preceding the line the language processor
found in error. Each error message is turned into a one line comment for
the language, and is internally flagged with the string ``###'' at the
beginning of the error, and ``%%%'' at the end of the error. This makes
pattern searching for errors easier with an editor, and allows the mes-
sages to be easily removed. In addition, each error message contains the
source line number for the line the message refers to. A reasonably for-
matted source program can be recompiled with the error messages still in
it, without having the error messages themselves cause future errors.
For poorly formatted source programs in free format languages, such as C
or Pascal, it is possible to insert a comment into another comment, which
can wreak havoc with a future compilation. To avoid this, programs with
comments and source on the same line should be formatted so that language
statements appear before comments.
EErrrroorr catches interrupt and terminate signals, and if in the insertion
phase, will orderly terminate what it is doing.
FFIILLEESS
~/._e_r_r_o_r_r_c function names to ignore for lint(1) error messages
/_d_e_v/_t_t_y user's teletype
HHIISSTTOORRYY
EErrrroorr appeared in 4.0 BSD.
AAUUTTHHOORR
Robert Henry
BBUUGGSS
Opens the teletype directly to do user querying.
Source files with links make a new copy of the file with only one link to
it.
Changing a language processor's format of error messages may cause eerrrroorr
to not understand the error message.
EErrrroorr, since it is purely mechanical, will not filter out subsequent er-
rors caused by `floodgating' initiated by one syntactically trivial er-
ror. Humans are still much better at discarding these related errors.
Pascal error messages belong after the lines affected (error puts them
before). The alignment of the `\' marking the point of error is also
disturbed by eerrrroorr.
EErrrroorr was designed for work on CRT's at reasonably high speed. It is
less pleasant on slow speed terminals, and has never been used on hard-
copy terminals.