Output Listings And Error Handling; General Information - HP eld Manual

6

Output Listings and Error Handling

This section contains the following topics:

General Information

Error Messages
Glossary of Errors
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:
Table 6-1. Completion Codes - The Severity Levels of Messages
Severity Type of
Level Message
3 fatal error
2 error
1 warning
0 information
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.
- when and how messages are created.
- individual cause, effect and recovery information.
- further detail on some of the error message text .
Meaning
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.
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.
The linker can do what was requested of it, but the linker isn't
sure that this is what the user really wanted.
This is not indicative of a problem.
eld Manual—527255-009
6-1