maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/tools/llvm-objdump/llvm-objdump.h

112 lines
4.4 KiB
C
Raw Normal View History

Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
//
// The LLVM Compiler Infrastructure
//
// This file is distributed under the University of Illinois Open Source
// License. See LICENSE.TXT for details.
//
//===----------------------------------------------------------------------===//
Canonicalize header guards into a common format. Add header guards to files that were missing guards. Remove #endif comments as they don't seem common in LLVM (we can easily add them back if we decide they're useful) Changes made by clang-tidy with minor tweaks. llvm-svn: 215558
2014-08-14 00:26:38 +08:00
#ifndef LLVM_TOOLS_LLVM_OBJDUMP_LLVM_OBJDUMP_H
#define LLVM_TOOLS_LLVM_OBJDUMP_LLVM_OBJDUMP_H
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
Re-submit r256008 "Improve DWARFDebugFrame::parse to also handle __eh_frame." Originally this change was causing failures on windows buildbots. But those problems were fixed in r258806. llvm-svn: 258811
2016-01-26 23:09:42 +08:00
#include "llvm/DebugInfo/DIContext.h"
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
#include "llvm/Support/CommandLine.h"
[llvm-objdump] Mark noreturn function as such. Match attribute in the header to make MSVC happy. llvm-svn: 256560
2015-12-29 21:41:02 +08:00
#include "llvm/Support/Compiler.h"
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
#include "llvm/Support/DataTypes.h"
Change llvm-objdump, llvm-nm and llvm-size when reporting an object file error when the object is in an archive to use something like libx.a(foo.o) as part of the error message. Also changed llvm-objdump and llvm-size to be like llvm-nm and ignore non-object files in archives and not produce any error message. To do this Archive::Child::getAsBinary() was changed from ErrorOr<...> to Expected<...> then that was threaded up to its users. Converting this interface to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now the use of errorToErrorCode() is still used in one place yet to be fully converted. Again there some were bugs in the existing code that did not deal with the old ErrorOr<> return values.  So now with Expected<> since they must be checked and the error handled, I added a TODO and a comments for those. llvm-svn: 269784
2016-05-18 01:10:12 +08:00
#include "llvm/Object/Archive.h"
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
namespace llvm {
[NFC] Header cleanup Removed some unused headers, replaced some headers with forward class declarations. Found using simple scripts like this one: clear && ack --cpp -l '#include "llvm/ADT/IndexedMap.h"' | xargs grep -L 'IndexedMap[<]' | xargs grep -n --color=auto 'IndexedMap' Patch by Eugene Kosov <claprix@yandex.ru> Differential Revision: http://reviews.llvm.org/D19219 From: Mehdi Amini <mehdi.amini@apple.com> llvm-svn: 266595
2016-04-18 17:17:29 +08:00
class StringRef;
Add dump of Win64 EH unwind data. The new command line option -unwind-info dumps the Win64 EH unwind data to the console. This is a nice feature if you need to debug generated EH data (e.g. from LLVM). Includes a test case. Initial patch by João Matos, extensions and rework by Kai Nacke. llvm-svn: 169415
2012-12-06 04:12:35 +08:00
namespace object {
class COFFObjectFile;
llvm-objdump: add coff import library symbol listing support This adds behaviour similar to binutils' objdump which can show symbols in an import library. Differences from that stem around the fact that we do not create section symbols nor the all import import descriptor symbol reference. However, this does mean that the tool can serve as a possible replacement for the existing tool. llvm-svn: 279088
2016-08-19 00:39:19 +08:00
class COFFImportFile;
llvm-objdump: implement printing for MachO __compact_unwind info. llvm-svn: 214509
2014-08-01 21:07:19 +08:00
class MachOObjectFile;
[objdump] Add --private-headers, -p. This currently prints the ELF program headers. llvm-svn: 171649
2013-01-06 11:56:49 +08:00
class ObjectFile;
Change llvm-objdump, llvm-nm and llvm-size when reporting an object file error when the object is in an archive to use something like libx.a(foo.o) as part of the error message. Also changed llvm-objdump and llvm-size to be like llvm-nm and ignore non-object files in archives and not produce any error message. To do this Archive::Child::getAsBinary() was changed from ErrorOr<...> to Expected<...> then that was threaded up to its users. Converting this interface to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now the use of errorToErrorCode() is still used in one place yet to be fully converted. Again there some were bugs in the existing code that did not deal with the old ErrorOr<> return values.  So now with Expected<> since they must be checked and the error handled, I added a TODO and a comments for those. llvm-svn: 269784
2016-05-18 01:10:12 +08:00
class Archive;
Add dump of Win64 EH unwind data. The new command line option -unwind-info dumps the Win64 EH unwind data to the console. This is a nice feature if you need to debug generated EH data (e.g. from LLVM). Includes a test case. Initial patch by João Matos, extensions and rework by Kai Nacke. llvm-svn: 169415
2012-12-06 04:12:35 +08:00
class RelocationRef;
}
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
extern cl::opt<std::string> TripleName;
extern cl::opt<std::string> ArchName;
Add the -mcpu= option to llvm-objdump for use with the disassemblers. Also make the disassembler created with the Mach-O parser (the -m option) pick up the Target specific attributes specified with -mattr option. llvm-svn: 215032
2014-08-07 07:24:41 +08:00
extern cl::opt<std::string> MCPU;
extern cl::list<std::string> MAttrs;
[llvm-objdump] Merging MachO DumpSections in to FilterSections. Simplifying some predicate logic. llvm-svn: 243556
2015-07-30 03:08:10 +08:00
extern cl::list<std::string> FilterSections;
[llvm-objdump] Added -j flag to filter sections that are operated on. llvm-svn: 243526
2015-07-29 23:45:39 +08:00
extern cl::opt<bool> Disassemble;
[llvm-objdump] Add -D and --disassemble-all flags that attempt disassembly on all sections instead of just text sections. llvm-svn: 243041
2015-07-24 04:58:49 +08:00
extern cl::opt<bool> DisassembleAll;
Flush out enough of llvm-objdump’s SymbolizerSymbolLookUp() for Mach-O files to get the literal string “Hello world” printed as a comment on the instruction that loads the pointer to it. For now this is just for x86_64. So for object files with relocation entries it produces things like: leaq L_.str(%rip), %rax ## literal pool for: "Hello world\n" and similar for fully linked images like executables: leaq 0x4f(%rip), %rax ## literal pool for: "Hello world\n" Also to allow testing against darwin’s otool(1), I hooked up the existing -no-show-raw-insn option to the Mach-O parser code, added the new Mach-O only -full-leading-addr option to match otool(1)'s printing of addresses and also added the new -print-imm-hex option. llvm-svn: 218423
2014-09-25 07:08:22 +08:00
extern cl::opt<bool> NoShowRawInsn;
Slightly refactor things for llvm-objdump and the -macho option so it can be used with options other than just -disassemble so that universal files can be used with other options combined with -arch options. No functional change to existing options and use. One test case added for the additional functionality with a universal file an a -arch option. llvm-svn: 225383
2015-01-08 05:02:18 +08:00
extern cl::opt<bool> PrivateHeaders;
For llvm-objdump, add the option -private-header (without the trailing ’s’) to only print the first private header. Which for Mach-O files only prints the Mach header and not the subsequent load commands. Which is used by scripts to match what the darwin otool(1) with the -h flag does without the -l flag. For non-Mach-O files it has the same functionality as -private-headers (with the trailing ’s’). rdar://24158331 llvm-svn: 257548
2016-01-13 08:25:36 +08:00
extern cl::opt<bool> FirstPrivateHeader;
Slightly refactor things for llvm-objdump and the -macho option so it can be used with options other than just -disassemble so that universal files can be used with other options combined with -arch options. No functional change to existing options and use. One test case added for the additional functionality with a universal file an a -arch option. llvm-svn: 225383
2015-01-08 05:02:18 +08:00
extern cl::opt<bool> ExportsTrie;
extern cl::opt<bool> Rebase;
extern cl::opt<bool> Bind;
extern cl::opt<bool> LazyBind;
extern cl::opt<bool> WeakBind;
llvm-objdump: Replace the -macho -raw option with a generic -raw-clang-ast option that works with all object container formats. Now that clang modules/PCH are object containers this option is useful to to construct pipes like llvm-objdump -raw-clang-ast foo.pcm | llvm-bcanalyzer - to inspect the AST contents in a PCH container. Will be tested via clang. Belatedly addresses review feedback for r233390. llvm-svn: 241659
2015-07-08 10:04:15 +08:00
extern cl::opt<bool> RawClangAST;
Add the option, -universal-headers, used with -macho to print the Mach-O universal headers to llvm-objdump. llvm-svn: 225537
2015-01-10 03:22:37 +08:00
extern cl::opt<bool> UniversalHeaders;
Add the option, -archive-headers, used with -macho to print the Mach-O archive headers to llvm-objdump. llvm-svn: 226228
2015-01-16 07:19:11 +08:00
extern cl::opt<bool> ArchiveHeaders;
Add the option, -indirect-symbols, used with -macho to print the Mach-O indirect symbol table to llvm-objdump. llvm-svn: 226848
2015-01-23 02:55:27 +08:00
extern cl::opt<bool> IndirectSymbols;
Add the option, -data-in-code, to llvm-objdump used with -macho to print the Mach-O data in code table. llvm-svn: 226921
2015-01-24 02:52:17 +08:00
extern cl::opt<bool> DataInCode;
dd the option, -link-opt-hints to llvm-objdump used with -macho to print the Mach-O AArch64 linker optimization hints for ADRP code optimization. llvm-svn: 227246
2015-01-28 05:28:24 +08:00
extern cl::opt<bool> LinkOptHints;
Add the option, -info-plist to llvm-objdump used with -macho to print the Mach-O info plist section as strings. llvm-svn: 231974
2015-03-12 06:06:32 +08:00
extern cl::opt<bool> InfoPlist;
Add the options, -dylibs-used and -dylib-id to llvm-objdump used with -macho to print the Mach-O dynamic shared libraries used by a linked image or the library id of a shared library. llvm-svn: 232406
2015-03-17 04:08:09 +08:00
extern cl::opt<bool> DylibsUsed;
extern cl::opt<bool> DylibId;
Add the option -objc-meta-data to llvm-objdump used with -macho to print the Objective-C runtime meta data for Mach-O files. There are three types of Objective-C runtime meta data, Objc2 64-bit, Objc2 32-bit and Objc1 32-bit. This prints the first of these types. The changes to print the others will follow next. llvm-svn: 233840
2015-04-02 04:57:01 +08:00
extern cl::opt<bool> ObjcMetaData;
Add the option, -dis-symname to llvm-objdump used with -macho and -disassemble to disassemble just one symbol’s instructions. llvm-svn: 232503
2015-03-18 01:10:57 +08:00
extern cl::opt<std::string> DisSymName;
Add the option, -non-verbose to llvm-objdump used with -macho to print things using numeric values and not their symbolic constant names. The routines that print Mach-O stuff already had a verbose parameter and this change is just changing the passing true to passing !NonVerbose. With just a couple of fixes and a bunch of test case updates. llvm-svn: 232182
2015-03-14 01:56:32 +08:00
extern cl::opt<bool> NonVerbose;
For llvm-objdump, hook up existing options to work when using -macho (the Mach-O parser). llvm-svn: 226612
2015-01-21 05:47:46 +08:00
extern cl::opt<bool> Relocations;
extern cl::opt<bool> SectionHeaders;
extern cl::opt<bool> SectionContents;
extern cl::opt<bool> SymbolTable;
extern cl::opt<bool> UnwindInfo;
[objdump] Moving PrintImmHex out of MachODump and in to llvm-objdump and setting instprinter appropriately. llvm-svn: 239265
2015-06-08 05:07:17 +08:00
extern cl::opt<bool> PrintImmHex;
Re-submit r256008 "Improve DWARFDebugFrame::parse to also handle __eh_frame." Originally this change was causing failures on windows buildbots. But those problems were fixed in r258806. llvm-svn: 258811
2016-01-26 23:09:42 +08:00
extern cl::opt<DIDumpType> DwarfDumpType;
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
// Various helper functions.
[llvm-objdump] Call exit(1) on error, i.e. fail early. Previously we kept going on partly corrupted input, which might result in garbage being printed, or even worse, random crashes. Rafael mentioned that this is the GNU behavior as well, but after some discussion we both agreed it's probably better to emit a reasonable error message and exit. As a side-effect of this commit, now we don't rely on global state for error codes anymore. objdump was the last tool in the toolchain which needed to be converted. Hopefully the old behavior won't sneak into the tree again. llvm-svn: 244019
2015-08-05 15:18:31 +08:00
void error(std::error_code ec);
Add dump of Win64 EH unwind data. The new command line option -unwind-info dumps the Win64 EH unwind data to the console. This is a nice feature if you need to debug generated EH data (e.g. from LLVM). Includes a test case. Initial patch by João Matos, extensions and rework by Kai Nacke. llvm-svn: 169415
2012-12-06 04:12:35 +08:00
bool RelocAddressLess(object::RelocationRef a, object::RelocationRef b);
Slightly refactor things for llvm-objdump and the -macho option so it can be used with options other than just -disassemble so that universal files can be used with other options combined with -arch options. No functional change to existing options and use. One test case added for the additional functionality with a universal file an a -arch option. llvm-svn: 225383
2015-01-08 05:02:18 +08:00
void ParseInputMachO(StringRef Filename);
Add dump of Win64 EH unwind data. The new command line option -unwind-info dumps the Win64 EH unwind data to the console. This is a nice feature if you need to debug generated EH data (e.g. from LLVM). Includes a test case. Initial patch by João Matos, extensions and rework by Kai Nacke. llvm-svn: 169415
2012-12-06 04:12:35 +08:00
void printCOFFUnwindInfo(const object::COFFObjectFile* o);
llvm-objdump: implement printing for MachO __compact_unwind info. llvm-svn: 214509
2014-08-01 21:07:19 +08:00
void printMachOUnwindInfo(const object::MachOObjectFile* o);
Object/llvm-objdump: allow dumping of mach-o exports trie 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
2014-08-30 08:20:14 +08:00
void printMachOExportsTrie(const object::MachOObjectFile* o);
[llvm-objdump] support -rebase option for mach-o to dump rebasing info Similar to my previous -exports-trie option, the -rebase option dumps info from the LC_DYLD_INFO load command. The rebasing info is a list of the the locations that dyld needs to adjust if a mach-o image is not loaded at its preferred address. Since ASLR is now the default, images almost never load at their preferred address, and thus need to be rebased by dyld. llvm-svn: 217709
2014-09-13 05:34:15 +08:00
void printMachORebaseTable(const object::MachOObjectFile* o);
[llvm-objdump] for mach-o add -bind, -lazy-bind, and -weak-bind options This finishes the ability of llvm-objdump to print out all information from the LC_DYLD_INFO load command. The -bind option prints out symbolic references that dyld must resolve immediately. The -lazy-bind option prints out symbolc reference that are lazily resolved on first use. The -weak-bind option prints out information about symbols which dyld must try to coalesce across images. llvm-svn: 217853
2014-09-16 09:41:51 +08:00
void printMachOBindTable(const object::MachOObjectFile* o);
void printMachOLazyBindTable(const object::MachOObjectFile* o);
void printMachOWeakBindTable(const object::MachOObjectFile* o);
[objdump] Add --private-headers, -p. This currently prints the ELF program headers. llvm-svn: 171649
2013-01-06 11:56:49 +08:00
void printELFFileHeader(const object::ObjectFile *o);
Re-submit r191472 with a fix for big endian. llvm-objdump: Dump COFF import table if -private-headers option is given. llvm-svn: 191557
2013-09-28 05:04:00 +08:00
void printCOFFFileHeader(const object::ObjectFile *o);
llvm-objdump: add coff import library symbol listing support This adds behaviour similar to binutils' objdump which can show symbols in an import library. Differences from that stem around the fact that we do not create section symbols nor the all import import descriptor symbol reference. However, this does mean that the tool can serve as a possible replacement for the existing tool. llvm-svn: 279088
2016-08-19 00:39:19 +08:00
void printCOFFSymbolTable(const object::COFFImportFile *i);
[llvm-objdump] Move COFF function to where it belongs. Ideally much more stuff should be moved out of llvm-objdump.cpp, but that will happen later. llvm-svn: 256118
2015-12-20 17:54:34 +08:00
void printCOFFSymbolTable(const object::COFFObjectFile *o);
Add the start of the support for llvm-objdump’s -private-headers for Mach-O files. This adds the printing of the mach header. Load command printing will be next. llvm-svn: 216285
2014-08-23 04:35:18 +08:00
void printMachOFileHeader(const object::ObjectFile *o);
For llvm-objdump, add the option -private-header (without the trailing ’s’) to only print the first private header. Which for Mach-O files only prints the Mach header and not the subsequent load commands. Which is used by scripts to match what the darwin otool(1) with the -h flag does without the -l flag. For non-Mach-O files it has the same functionality as -private-headers (with the trailing ’s’). rdar://24158331 llvm-svn: 257548
2016-01-13 08:25:36 +08:00
void printMachOLoadCommands(const object::ObjectFile *o);
[WebAssembly] Add llvm-objdump support for wasm file format This is the first part of an effort to add wasm binary support across all llvm tools. Patch by Sam Clegg Differential Revision: https://reviews.llvm.org/D26172 llvm-svn: 288251
2016-12-01 00:49:11 +08:00
void printWasmFileHeader(const object::ObjectFile *o);
Slightly refactor things for llvm-objdump and the -macho option so it can be used with options other than just -disassemble so that universal files can be used with other options combined with -arch options. No functional change to existing options and use. One test case added for the additional functionality with a universal file an a -arch option. llvm-svn: 225383
2015-01-08 05:02:18 +08:00
void printExportsTrie(const object::ObjectFile *o);
void printRebaseTable(const object::ObjectFile *o);
void printBindTable(const object::ObjectFile *o);
void printLazyBindTable(const object::ObjectFile *o);
void printWeakBindTable(const object::ObjectFile *o);
llvm-objdump: Replace the -macho -raw option with a generic -raw-clang-ast option that works with all object container formats. Now that clang modules/PCH are object containers this option is useful to to construct pipes like llvm-objdump -raw-clang-ast foo.pcm | llvm-bcanalyzer - to inspect the AST contents in a PCH container. Will be tested via clang. Belatedly addresses review feedback for r233390. llvm-svn: 241659
2015-07-08 10:04:15 +08:00
void printRawClangAST(const object::ObjectFile *o);
For llvm-objdump, hook up existing options to work when using -macho (the Mach-O parser). llvm-svn: 226612
2015-01-21 05:47:46 +08:00
void PrintRelocations(const object::ObjectFile *o);
void PrintSectionHeaders(const object::ObjectFile *o);
void PrintSectionContents(const object::ObjectFile *o);
Change llvm-objdump, llvm-nm and llvm-size when reporting an object file error when the object is from a slice of a Mach-O Universal Binary use something like "foo.o (for architecture i386)" as part of the error message when expected. Also fixed places in these tools that were ignoring object file errors from MachOUniversalBinary::getAsObjectFile() when the code moved on to see if the slice was an archive. To do this MachOUniversalBinary::getAsObjectFile() and MachOUniversalBinary::getObjectForArch() were changed from returning ErrorOr<...> to Expected<...> then that was threaded up to its users. Converting these interfaces to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now the use of errorToErrorCode() is still used in two places yet to be fully converted. llvm-svn: 271332
2016-06-01 04:35:34 +08:00
void PrintSymbolTable(const object::ObjectFile *o, StringRef ArchiveName,
StringRef ArchitectureName = StringRef());
Finish cleaning up most of the error handling in libObject’s MachOUniversalBinary and its clients to use the new llvm::Error model for error handling. Changed getAsArchive() from ErrorOr<...> to Expected<...> so now all interfaces there use the new llvm::Error model for return values. In the two places it had if (!Parent) this is actually a program error so changed from returning errorCodeToError(object_error::parse_failed) to calling report_fatal_error() with a message. In getObjectForArch() added error messages to its two llvm::Error return values instead of returning errorCodeToError(object_error::arch_not_found) with no error message. For the llvm-obdump, llvm-nm and llvm-size clients since the only binary files in Mach-O Universal Binaries that are supported are Mach-O files or archives with Mach-O objects, updated their logic to generate an error when a slice contains something like an ELF binary instead of ignoring it. And added a test case for that. The last error stuff to be cleaned up for libObject’s MachOUniversalBinary is the use of errorOrToExpected(Archive::create(ObjBuffer)) which needs Archive::create() to be changed from ErrorOr<...> to Expected<...> first, which I’ll work on next. llvm-svn: 274079
2016-06-29 07:16:13 +08:00
LLVM_ATTRIBUTE_NORETURN void error(Twine Message);
General clean up of error handling in llvm-objdump to remove its use of report_fatal_error(). No real functional change with this commit. The problem with report_fatal_error() is it does not include the tool name and the file name the for which the error message was generated. Uses of report_fatal_error() were change to report_error() or error() to get a better error and to make the code smaller and cleaner. Also changed things like error(errorToErrorCode(SOrErr.takeError())) to use report_error() with a file name and the llvm::Error (as well as the ArchitectureName if available) so the error message is printed. llvm-svn: 287163
2016-11-17 06:17:38 +08:00
LLVM_ATTRIBUTE_NORETURN void report_error(StringRef File, Twine Message);
[llvm-objdump] Mark noreturn function as such. Match attribute in the header to make MSVC happy. llvm-svn: 256560
2015-12-29 21:41:02 +08:00
LLVM_ATTRIBUTE_NORETURN void report_error(StringRef File, std::error_code EC);
Thread Expected<...> up from createMachOObjectFile() to allow llvm-objdump to produce a real error message Produce the first specific error message for a malformed Mach-O file describing the problem instead of the generic message for object_error::parse_failed of "Invalid data was encountered while parsing the file”.  Many more good error messages will follow after this first one. This is built on Lang Hames’ great work of adding the ’Error' class for structured error handling and threading Error through MachOObjectFile construction. And making createMachOObjectFile return Expected<...> . So to to get the error to the llvm-obdump tool, I changed the stack of these methods to also return Expected<...> : object::ObjectFile::createObjectFile() object::SymbolicFile::createSymbolicFile() object::createBinary() Then finally in ParseInputMachO() in MachODump.cpp the error can be reported and the specific error message can be printed in llvm-objdump and can be seen in the existing test case for the existing malformed binary but with the updated error message. Converting these interfaces to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now use of errorToErrorCode() and errorOrToExpected() are used where the callers are yet to be converted. Also there some were bugs in the existing code that did not deal with the old ErrorOr<> return values. So now with Expected<> since they must be checked and the error handled, I added a TODO and a comment: “// TODO: Actually report errors helpfully” and a call something like consumeError(ObjOrErr.takeError()) so the buggy code will not crash since needed to deal with the Error. Note there is one fix also needed to lld/COFF/InputFiles.cpp that goes along with this that I will commit right after this. So expect lld not to built after this commit and before the next one. llvm-svn: 265606
2016-04-07 06:14:09 +08:00
LLVM_ATTRIBUTE_NORETURN void report_error(StringRef File, llvm::Error E);
Change llvm-objdump, llvm-nm and llvm-size when reporting an object file error when the object is in an archive to use something like libx.a(foo.o) as part of the error message. Also changed llvm-objdump and llvm-size to be like llvm-nm and ignore non-object files in archives and not produce any error message. To do this Archive::Child::getAsBinary() was changed from ErrorOr<...> to Expected<...> then that was threaded up to its users. Converting this interface to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now the use of errorToErrorCode() is still used in one place yet to be fully converted. Again there some were bugs in the existing code that did not deal with the old ErrorOr<> return values.  So now with Expected<> since they must be checked and the error handled, I added a TODO and a comments for those. llvm-svn: 269784
2016-05-18 01:10:12 +08:00
LLVM_ATTRIBUTE_NORETURN void report_error(StringRef FileName,
StringRef ArchiveName,
Change llvm-objdump, llvm-nm and llvm-size when reporting an object file error when the object is from a slice of a Mach-O Universal Binary use something like "foo.o (for architecture i386)" as part of the error message when expected. Also fixed places in these tools that were ignoring object file errors from MachOUniversalBinary::getAsObjectFile() when the code moved on to see if the slice was an archive. To do this MachOUniversalBinary::getAsObjectFile() and MachOUniversalBinary::getObjectForArch() were changed from returning ErrorOr<...> to Expected<...> then that was threaded up to its users. Converting these interfaces to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now the use of errorToErrorCode() is still used in two places yet to be fully converted. llvm-svn: 271332
2016-06-01 04:35:34 +08:00
llvm::Error E,
StringRef ArchitectureName
= StringRef());
Change llvm-objdump, llvm-nm and llvm-size when reporting an object file error when the object is in an archive to use something like libx.a(foo.o) as part of the error message. Also changed llvm-objdump and llvm-size to be like llvm-nm and ignore non-object files in archives and not produce any error message. To do this Archive::Child::getAsBinary() was changed from ErrorOr<...> to Expected<...> then that was threaded up to its users. Converting this interface to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now the use of errorToErrorCode() is still used in one place yet to be fully converted. Again there some were bugs in the existing code that did not deal with the old ErrorOr<> return values.  So now with Expected<> since they must be checked and the error handled, I added a TODO and a comments for those. llvm-svn: 269784
2016-05-18 01:10:12 +08:00
LLVM_ATTRIBUTE_NORETURN void report_error(StringRef ArchiveName,
const object::Archive::Child &C,
Change llvm-objdump, llvm-nm and llvm-size when reporting an object file error when the object is from a slice of a Mach-O Universal Binary use something like "foo.o (for architecture i386)" as part of the error message when expected. Also fixed places in these tools that were ignoring object file errors from MachOUniversalBinary::getAsObjectFile() when the code moved on to see if the slice was an archive. To do this MachOUniversalBinary::getAsObjectFile() and MachOUniversalBinary::getObjectForArch() were changed from returning ErrorOr<...> to Expected<...> then that was threaded up to its users. Converting these interfaces to Expected<> from ErrorOr<> does involve touching a number of places. To contain the changes for now the use of errorToErrorCode() is still used in two places yet to be fully converted. llvm-svn: 271332
2016-06-01 04:35:34 +08:00
llvm::Error E,
StringRef ArchitectureName
= StringRef());
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
Re-submit r191472 with a fix for big endian. llvm-objdump: Dump COFF import table if -private-headers option is given. llvm-svn: 191557
2013-09-28 05:04:00 +08:00
} // end namespace llvm
Add a MachO-specific "mode" to llvm-objdump, that, if enabled, gathers additional information that are only available on MachO. - It can take FunctionStarts from a binary to find entry points more accurately. - Symbol offsets in executables are correct now. llvm-svn: 140028
2011-09-20 01:56:04 +08:00
#endif