eld Manual—527255-009
6-1
6
Output Listings and Error Handling
This section contains the following topics:
General Information
- when and how messages are created.
Error Messages
- individual cause, effect and recovery information.
Glossary of Errors
- further detail on some of the error message text .
General Information
The linker creates a listing file that is written to the C standard output file.
eld
does
not override whatever default rules are provided for the standard output file by the C
runtime on each platform. For example, if it is not possible to open the standard output
file, and the default behavior of the C runtime is to write out a message on standard
error in such a situation, then that is what will happen. Also, note that when you put
standard output into a file on Guardian, it gets appended to what was in that file before,
rather than overwriting the file (this is "normal" Guardian behavior; for example, FUP
does the same thing).
Messages that appear in the output listing fall into the following four severity levels:
On Guardian
eld
's return code is equal to the highest severity level that occurred
during the link, i.e., 0, 1, 2, or 3. That is done because this is a Guardian standard. On
the other hand, on the PC and OSS, users are accustomed to just checking whether
the value is 0 or 1, and considering 1 to be an error, and not caring about warnings.
So, on the PC and OSS,
eld
calls exit with a parameter value of 0 if the highest
severity was 0 or 1, and with a parameter value of 1 if the highest severity level was 2
or 3.
Table 6-1. Completion Codes - The Severity Levels of Messages
Severity
Level
Type of
Message
Meaning
3
fatal error
The linker cannot do what was requested of it and the linker
immediately stops. This includes all cases of command
stream syntax errors, I/O errors, and memory allocation
errors.
2
error
The linker cannot do what was requested of it and will
eventually stop, but may continue for the purpose of
detecting additional errors before stopping.
1
warning
The linker can do what was requested of it, but the linker isn’t
sure that this is what the user really wanted.
0
information
This is not indicative of a problem.
Summary of Contents for eld
Page 4: ......
Page 8: ...Contents eld Manual 527255 009 iv ...
Page 12: ...What s New in This Manual eld Manual 527255 009 viii Changes to the 527255 005 Manual ...
Page 34: ...Introduction to eld eld Manual 527255 009 1 14 Example of Use ...
Page 54: ...eld Input and Output eld Manual 527255 009 2 20 Using Archives ...
Page 98: ...Other eld Processing eld Manual 527255 009 4 20 Merging Source RTDUs ...
Page 242: ...Output Listings and Error Handling eld Manual 527255 009 6 132 Glossary of Errors ...