Keil Logo

List of the fromelf error and warning messages

5.1 List of the fromelf error and warning messages

Lists the error and warning messages that fromelf produces.

Note

License-related error messages can be found in the 2.1 List of the licensing error and warning messages section.
Q0105E: Load region #<segindex> extends beyond top of address space.
Q0106E: Out of Memory.
Q0107E: Failed writing output file '<filename>': <reason>
Q0108E: Could not create output file '<filename>': <reason>
Q0119E: No output file specified.
Q0120E: No input file specified.
Q0122E: Could not open file '<filename>': <reason>
If <reason> is Invalid argument, this might be because you have invalid characters on the command line.
See the following in the fromelf User Guide:
Q0128E: File i/o failure.
This error can occur if you specify a directory for the --output command-line option, but you did not terminate the directory with a path separator. For example, --output=my_elf_files/.
See the following in the fromelf User Guide:
Q0129E: Not a 32 bit ELF file.
Q0130E: Not a 64 bit ELF file.
Q0131E: Invalid ELF identification number found.
This error is given if you attempt to use fromelf on a file which is not in ELF format, or which is corrupted. Object (.o) files and executable (.axf) files are in ELF format.
Q0132E: Invalid ELF section index found <idx>.
Q0133E: Invalid ELF segment index found <idx>.
Q0134E: Invalid ELF string table index found <idx>.
Q0135E: Invalid ELF section entry size found.
Q0136E: ELF Header contains invalid file type.
Q0137E: ELF Header contains invalid machine name.
Q0138E: ELF Header contains invalid version number.
See Q0131E.
Q0147E: Failed to create Directory <dir>: <reason>
If <reason> is File exists, this might be because you have specified a directory that has the same name as a file that already exists. For example, if a file called filtered already exists, then the following command produces this error:
fromelf --elf --strip=all t.a(test*.o) -o filtered/
The path separator character / informs fromelf that filtered is a directory.
See the following in the fromelf User Guide:
Q0171E: Invalid st_name index into string table <idx>.
See Q0131E.
Q0172E: Invalid index into symbol table <idx>.
See Q0131E.
Q0186E: This option requires debugging information to be present
The --fieldoffsets option requires the image to be built with dwarf debug tables.
Q0425W: Incorrectly formed virtual function elimination header in file
This might indicate a compiler fault. Contact your supplier.
Q0426E: Error reading vtable information from file
This might indicate a compiler fault. Contact your supplier.
Q0427E: Error getting string for symbol in a vtable
This might indicate a compiler fault. Contact your supplier.
Q0433E: Diagnostic style <style> not recognised
Q0440E: No relocation sections for <secname>
Q0447W: Unknown Diagnostic number (<num>)
Q0448W: Read past the end of the compressed data while decompressing section '<secname>' #<secnum> in <file>
This might indicate an internal fault. Contact your supplier.
Q0449W: Write past the end of the uncompressed data buffer of size <bufsize> while decompressing section '<secname>' #<secnum> in <file>
This might indicate an internal fault. Contact your supplier.
Q0450W: Section '<secname>' #<secnum> in file <file> uses a mixture of legacy and current ABI relocation types.
Q0451W: Option '--strip symbols' used without '--strip debug' on an ELF file that has debug information.
Q0452W: Option '--strip filesymbols' used without '--strip debug' on an ELF file that has debug information.
Q0453W: Stripping path names from '<path1>' and '<path2>' produces a duplicate file name '<filename>'.
Q0454E: In ELF file: <details>
Non-ConfidentialPDF file icon PDF versionARM DUI0591F
Copyright © 2011, 2012, 2014-2016 ARM. All rights reserved. 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.