Output Listings and Error Handling
eld Manual—527255-009
6-4
Error Messages
eld
breaks the message at a space if possible. When a message is broken at a
space, the space is left at the end of the broken line.
eld
demangles C++ symbol names in listing messages, as follows. Any name that
contains two consecutive underscores is assumed to be a C++ name, and
eld
tries to
demangle it, using a demangling algorithm that tries to be consistent with the mangling
done by the C++ compiler. If a name cannot be successfully demangled,
eld
writes
out the name as it found it. If a name can be demangled,
eld
writes out both the
original and the demangled form.
Error Messages
This section contains detailed error messages with cause, effect and recovery
information where necessary.
The table shows all the messages that could normally appear during
eld
's operation.
There is no particular significance to any of the message numbers. Following the table
there is a
Glossary of Errors
on page 6-126 that provides more help based directly on
the words that appear in the messages.
It is also possible that you may see a message that begins with the string "Internal
error" or "Bad input file", not listed in this section. In some cases, the message may
help you resolve the problem at hand. If you cannot resolve such a problem, or if any
other message appears that is not listed in the table below, or if
eld
terminates
abnormally, that is probably something to be reported as a possible
eld
bug to your
HP representative. If
eld
complained about an input file, that might also indicate a
bug in some other tool that created that input file.
Cause.
This message may appear in one of two scenarios. One is that you gave the
-make_import_lib
option, specifying the names of one or more existing DLLs on
the command line, and the filename mentioned in the message is one of those names.
The other is that you gave the
-change
option, and the filename mentioned in the
message is the name of the existing file that you intend to update. In either case, the
specified file doesn’t exist or you don’t have permission to read it.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
Recovery.
Check that you really intended to specify a file of the indicated name, that
you spelled it correctly, and that you have permission to read it.
1000 Cannot open file <filename>.
1004 The addresses of the two memory areas overlap: the text
memory area goes from <address> to <address>, and the data
memory area goes from <address> to <address>.
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 ...