Microchip Technology SW006021-2 Manual Do Utilizador
MPLAB
®
XC8 C COMPILER
USER’S GUIDE
2012 Microchip Technology Inc.
DS52053B-page 377
Appendix B. Error and Warning Messages
This chapter lists the MPLAB XC8 C Compiler error, warning and advisory messages
with an explanation of each message. This is the complete and historical message set
covering all former HI-TECH C compilers and all compiler versions. Not all messages
shown here may be relevant for the compiler version you are using.
with an explanation of each message. This is the complete and historical message set
covering all former HI-TECH C compilers and all compiler versions. Not all messages
shown here may be relevant for the compiler version you are using.
Most messages have been assigned a unique number which appears in brackets
before each message description, and which is also printed by the compiler when the
message is issued. The messages shown here are sorted by their number. Un-num-
bered messages appear toward the end and are sorted alphabetically.
before each message description, and which is also printed by the compiler when the
message is issued. The messages shown here are sorted by their number. Un-num-
bered messages appear toward the end and are sorted alphabetically.
The name of the application(s) that could have produced the messages are listed in
brackets opposite the error message. In some cases examples of code or options that
could trigger the error are given. The use of * in the error message is used to represent
a string that the compiler will substitute that is specific to that particular error.
brackets opposite the error message. In some cases examples of code or options that
could trigger the error are given. The use of * in the error message is used to represent
a string that the compiler will substitute that is specific to that particular error.
Note that one problem in your C or assembler source code may trigger more than one
error message. You should attempt to resolve errors or warnings in the order in which
they are produced.
error message. You should attempt to resolve errors or warnings in the order in which
they are produced.
MESSAGES 1-249
(1) too many errors (*)
(all applications)
The executing compiler application has encountered too many errors and will exit
immediately. Other uncompiled source files will be processed, but the compiler appli-
cations that would normally be executed in due course will not be run. The number of
errors that can be accepted can be controlled using the --ERRORS option, See
Section 4.8.29 “--ERRORS: Maximum Number of Errors”.
immediately. Other uncompiled source files will be processed, but the compiler appli-
cations that would normally be executed in due course will not be run. The number of
errors that can be accepted can be controlled using the --ERRORS option, See
Section 4.8.29 “--ERRORS: Maximum Number of Errors”.
(2)
error/warning (*) generated, but no description available
(all applications)
The executing compiler application has emitted a message (advisory/warning/error),
but there is no description available in the message description file (MDF) to print. This
may be because the MDF is out of date, or the message issue has not been translated
into the selected language.
but there is no description available in the message description file (MDF) to print. This
may be because the MDF is out of date, or the message issue has not been translated
into the selected language.
(3) malformed error information on line
*
, in file
*
(all applications)
The compiler has attempted to load the messages for the selected language, but the
message description file (MDF) was corrupted and could not be read correctly.
message description file (MDF) was corrupted and could not be read correctly.
(100) unterminated #if[n][def] block from line *
(Preprocessor)
A #if or similar block was not terminated with a matching #endif, for example:
#if INPUT /* error flagged here */
void main(void)
{
run();
} /* no #endif was found in this module */