Be permissive about badly formed elf files.
Here is the allowable issues with an elf file that will not result in an error: - The program headers/section headers offset points to unreadable memory. - Allow missing program header and/or section headers. - Allow a symbol table section header to point to invalid symbol table values. There is no real reason to require the elf file be perfect. Everything in the code has sane defaults, so any missing information won't cause any problems. This gets rid of the warning that occurs any time an elf is loaded from memory. In memory elf files never contain all of the section headers, and do not contain the symbol table data. Update tests to test these new cases. Test: Builds and unit tests all pass. Change-Id: Iaefe2cd6b6c965a01ed425a112d6afae339f3b78
Loading
Please register or sign in to comment