summaryrefslogtreecommitdiffstats
path: root/llvm/test/tools/llvm-objdump/macho-exports-trie.test
Commit message (Collapse)AuthorAgeFilesLines
* Fix a FIXME in llvm-objdump for the -exports-trie option that was not addingKevin Enderby2017-06-191-0/+10
| | | | | | | | | | in the base address. Without this Mach-O files, like 64-bit executables, don’t have the correct addresses printed for their exports. As the default is to link at address 0x100000000 not zero. llvm-svn: 305744
* Fix test case to match correct llvm-objdump outputNick Kledzik2014-09-031-3/+3
| | | | llvm-svn: 217006
* Object/llvm-objdump: allow dumping of mach-o exports trieNick Kledzik2014-08-301-0/+11
MachOObjectFile in lib/Object currently has no support for parsing the rebase, binding, and export information from the LC_DYLD_INFO load command in final linked mach-o images. This patch adds support for parsing the exports trie data structure. It also adds an option to llvm-objdump to dump that export info. I did the exports parsing first because it is the hardest. The information is encoded in a trie structure, but the standard ObjectFile way to inspect content is through iterators. So I needed to make an iterator that would do a non-recursive walk through the trie and maintain the concatenation of edges needed for the current string prefix. I plan to add similar support in MachOObjectFile and llvm-objdump to parse/display the rebasing and binding info too. llvm-svn: 216808
OpenPOWER on IntegriCloud