llvm-mirror/tools/llvm-pdbutil/CMakeLists.txt

set(LLVM_LINK_COMPONENTS
  BinaryFormat
  DebugInfoCodeView
  DebugInfoMSF
  DebugInfoPDB
  Object
  ObjectYAML
  Support
  )

add_llvm_tool(llvm-pdbutil
  BytesOutputStyle.cpp
  DumpOutputStyle.cpp
  ExplainOutputStyle.cpp
  InputFile.cpp
  llvm-pdbutil.cpp
  FormatUtil.cpp
  LinePrinter.cpp
  MinimalSymbolDumper.cpp
  MinimalTypeDumper.cpp
  PdbYaml.cpp
  PrettyBuiltinDumper.cpp
  PrettyClassDefinitionDumper.cpp
  PrettyClassLayoutGraphicalDumper.cpp
  PrettyCompilandDumper.cpp
  PrettyEnumDumper.cpp
  PrettyExternalSymbolDumper.cpp
  PrettyFunctionDumper.cpp
  PrettyTypeDumper.cpp
  PrettyTypedefDumper.cpp
  PrettyVariableDumper.cpp
  StreamUtil.cpp
  TypeReferenceTracker.cpp
  YAMLOutputStyle.cpp
  )
Rewrite llvm-pdbdump in terms of LLVMDebugInfoPDB. This makes llvm-pdbdump available on all platforms, although it will currently fail to create a dumper if there is no PDB reader implementation for the current platform. It implements dumping of compilands and children, which is less information than was previously available, but it has to be rewritten from scratch using the new set of interfaces, so the rest of the functionality will be added back in subsequent commits. llvm-svn: 228755 2015-02-10 23:43:25 +01:00			`set(LLVM_LINK_COMPONENTS`
[llvm-pdbutil] Support dumping CodeView from object files. We have llvm-readobj for dumping CodeView from object files, and llvm-pdbutil has always been more focused on PDB. However, llvm-pdbutil has a lot of useful options for summarizing debug information in aggregate and presenting high level statistical views. Furthermore, it's arguably better as a testing tool since we don't have to write tests to conform to a state-machine like structure where you match multiple lines in succession, each depending on a previous match. llvm-pdbutil dumps much more concisely, so it's possible to use single-line matches in many cases where as with readobj tests you have to use multi-line matches with an implicit state machine. Because of this, I'm adding object file support to llvm-pdbutil. In fact, this mirrors the cvdump tool from Microsoft, which also supports both object files and pdb files. In the future we could perhaps rename this tool llvm-cvutil. In the meantime, this allows us to deep dive into object files the same way we already can with PDB files. llvm-svn: 312358 2017-09-01 22:06:56 +02:00			`BinaryFormat`
Make llvm-pdbdump print CV type records This reuses the CVTypeDumper from libcodeview to dump full information about type records within a PDB file. Differential Revision: http://reviews.llvm.org/D20022 Reviewed By: rnk llvm-svn: 268808 2016-05-07 00:15:42 +02:00			`DebugInfoCodeView`
[msf] Resubmit "Rename Msf -> MSF". Previously this change was submitted from a Windows machine, so changes made to the case of filenames and directory names did not survive the commit, and as a result the CMake source file names and the on-disk file names did not match on case-sensitive file systems. I'm resubmitting this patch from a Linux system, which hopefully allows the case changes to make it through unfettered. llvm-svn: 277213 2016-07-29 22:56:36 +02:00			`DebugInfoMSF`
Rewrite llvm-pdbdump in terms of LLVMDebugInfoPDB. This makes llvm-pdbdump available on all platforms, although it will currently fail to create a dumper if there is no PDB reader implementation for the current platform. It implements dumping of compilands and children, which is less information than was previously available, but it has to be rewritten from scratch using the new set of interfaces, so the rest of the functionality will be added back in subsequent commits. llvm-svn: 228755 2015-02-10 23:43:25 +01:00			`DebugInfoPDB`
llvm-pdbdump: Update libdeps. llvm-svn: 268464 2016-05-04 01:25:47 +02:00			`Object`
[CodeView] Move CodeView YAML code to ObjectYAML. This is the beginning of an effort to move the codeview yaml reader / writer into ObjectYAML so that it can be shared. Currently the only consumer / producer of CodeView YAML is llvm-pdbdump, but CodeView can exist outside of PDB files, and indeed is put into object files and passed to the linker to produce PDB files. Furthermore, there are subtle differences in the types of records that show up in object file CodeView vs PDB file CodeView, but they are otherwise 99% the same. By having this code in ObjectYAML, we can have llvm-pdbdump reuse this code, while teaching obj2yaml and yaml2obj to use this syntax for dealing with object files that can contain CodeView. This patch only adds support for CodeView type information to ObjectYAML. Subsequent patches will add support for CodeView symbol information. llvm-svn: 304248 2017-05-30 23:53:05 +02:00			`ObjectYAML`
llvm-pdbdump: Update libdeps. llvm-svn: 268464 2016-05-04 01:25:47 +02:00			`Support`
Rewrite llvm-pdbdump in terms of LLVMDebugInfoPDB. This makes llvm-pdbdump available on all platforms, although it will currently fail to create a dumper if there is no PDB reader implementation for the current platform. It implements dumping of compilands and children, which is less information than was previously available, but it has to be rewritten from scratch using the new set of interfaces, so the rest of the functionality will be added back in subsequent commits. llvm-svn: 228755 2015-02-10 23:43:25 +01:00			`)`
Run dos2unix against llvm-pdbdump. llvm-svn: 227262 2015-01-28 00:02:23 +01:00
Rename llvm-pdbdump -> llvm-pdbutil. This is to reflect the evolving nature of the tool as being useful for more than just dumping PDBs, as it can do many other things. Differential Revision: https://reviews.llvm.org/D34062 llvm-svn: 305106 2017-06-09 22:46:17 +02:00			`add_llvm_tool(llvm-pdbutil`
[llvm-pdbutil] Create a "bytes" subcommand. This idea originally came about when I was doing some deep investigation of why certain bytes in a PDB that we round-tripped differed from their original bytes in the source PDB. I found myself having to hack up the code in many places to dump the bytes of this substream, or that record. It would be nice if we could just do this for every possible stream, substream, debug chunk type, etc. It doesn't make sense to put this under dump because there's just so many options that would detract from the more common use case of just dumping deserialized records. So making a new subcommand seems like the most logical course of action. In doing so, we already have two command line options that are suitable for this new subcommand, so start out by moving them there. llvm-svn: 306056 2017-06-22 22:58:11 +02:00			`BytesOutputStyle.cpp`
[llvm-pdbutil] Rename "raw" to "dump". Now you run llvm-pdbutil dump <options>. This is a followup after having renamed the tool, whereas before raw was obviously just the style of dumping, whereas now "dump" is the action to perform with the "util". llvm-svn: 306055 2017-06-22 22:57:39 +02:00			`DumpOutputStyle.cpp`
[PDB] Add an explain subcommand. When investigating various things, we often have a file offset and what to know what's in the PDB at that address. For example we may be doing a binary comparison of two LLD-generated PDBs to look for sources of non-determinism, or we may wish to compare an LLD-generated PDB with a Microsoft generated PDB for sources of byte-for-byte incompatibility. In these cases, we can do a binary diff of the two files, and once we find a mismatched byte we can use explain to figure out what that byte is, immediately honining in on the problem. This patch implements this by trying to narrow the meaning of a particular file offset down as much as possible. Differential Revision: https://reviews.llvm.org/D44959 llvm-svn: 328799 2018-03-29 18:28:20 +02:00			`ExplainOutputStyle.cpp`
[llvm-pdbutil] Support dumping CodeView from object files. We have llvm-readobj for dumping CodeView from object files, and llvm-pdbutil has always been more focused on PDB. However, llvm-pdbutil has a lot of useful options for summarizing debug information in aggregate and presenting high level statistical views. Furthermore, it's arguably better as a testing tool since we don't have to write tests to conform to a state-machine like structure where you match multiple lines in succession, each depending on a previous match. llvm-pdbutil dumps much more concisely, so it's possible to use single-line matches in many cases where as with readobj tests you have to use multi-line matches with an implicit state machine. Because of this, I'm adding object file support to llvm-pdbutil. In fact, this mirrors the cvdump tool from Microsoft, which also supports both object files and pdb files. In the future we could perhaps rename this tool llvm-cvutil. In the meantime, this allows us to deep dive into object files the same way we already can with PDB files. llvm-svn: 312358 2017-09-01 22:06:56 +02:00			`InputFile.cpp`
Rename llvm-pdbdump -> llvm-pdbutil. This is to reflect the evolving nature of the tool as being useful for more than just dumping PDBs, as it can do many other things. Differential Revision: https://reviews.llvm.org/D34062 llvm-svn: 305106 2017-06-09 22:46:17 +02:00			`llvm-pdbutil.cpp`
Resubmit "[llvm-pdbutil] rewrite the "raw" output style." This resubmits commit c0c249e9f2ef83e1d1e5f166b50673d92f3579d7. It was broken due to some weird template issues, which have since been fixed. llvm-svn: 305517 2017-06-16 00:24:24 +02:00			`FormatUtil.cpp`
[llvm-pdbdump] Colorize output. llvm-svn: 230746 2015-02-27 10:15:59 +01:00			`LinePrinter.cpp`
Resubmit "[llvm-pdbutil] rewrite the "raw" output style." This resubmits commit c0c249e9f2ef83e1d1e5f166b50673d92f3579d7. It was broken due to some weird template issues, which have since been fixed. llvm-svn: 305517 2017-06-16 00:24:24 +02:00			`MinimalSymbolDumper.cpp`
			`MinimalTypeDumper.cpp`
[llvm-pdbdump] Dump MSF headers to YAML. This is the simplest possible patch to get some kind of YAML output. All it dumps is the MSF header fields so that in theory an empty MSF file could be reconstructed. Reviewed By: ruiu, majnemer Differential Revision: http://reviews.llvm.org/D20971 llvm-svn: 271939 2016-06-06 22:37:05 +02:00			`PdbYaml.cpp`
[CodeView/PDB] Rename a bunch of files. We were starting to get some name clashes between llvm-pdbdump and the common CodeView framework, so I took this opportunity to rename a bunch of files to more accurately describe their usage. This also helps in llvm-pdbdump to distinguish between different files and whether they are used for pretty dump mode or raw dump mode. llvm-svn: 291627 2017-01-11 01:35:43 +01:00			`PrettyBuiltinDumper.cpp`
			`PrettyClassDefinitionDumper.cpp`
[llvm-pdbdump] Minor prepatory refactor of Class Def Dumper. In a followup patch I intend to introduce an additional dumping mode which dumps a graphical representation of a class's layout. In preparation for this, the text-based layout printer needs to be split out from the graphical layout printer, and both need to be able to use the same code for printing the intro and outro of a class's definition (e.g. base class list, etc). This patch does so, and in the process introduces a skeleton definition for the graphical printer, while currently making the graphical printer just print nothing. NFC llvm-svn: 300134 2017-04-13 01:18:51 +02:00			`PrettyClassLayoutGraphicalDumper.cpp`
[CodeView/PDB] Rename a bunch of files. We were starting to get some name clashes between llvm-pdbdump and the common CodeView framework, so I took this opportunity to rename a bunch of files to more accurately describe their usage. This also helps in llvm-pdbdump to distinguish between different files and whether they are used for pretty dump mode or raw dump mode. llvm-svn: 291627 2017-01-11 01:35:43 +01:00			`PrettyCompilandDumper.cpp`
			`PrettyEnumDumper.cpp`
			`PrettyExternalSymbolDumper.cpp`
			`PrettyFunctionDumper.cpp`
			`PrettyTypeDumper.cpp`
			`PrettyTypedefDumper.cpp`
			`PrettyVariableDumper.cpp`
Add the beginning of PDB diffing support. For now this only diffs the stream directory and the MSF Superblock. Future patches will drill down into individual streams to find out where the differences lie. Differential Revision: https://reviews.llvm.org/D30908 llvm-svn: 297689 2017-03-14 00:28:25 +01:00			`StreamUtil.cpp`
[llvm-pdbutil] Add -type-ref-stats to help find unused type info Summary: This considers module symbol streams and the global symbol stream to be roots. Most types that this considers "unreferenced" are referenced by LF_UDT_MOD_SRC_LINE id records, which VC seems to always include. Essentially, they are types that the user can only find in the debugger if they call them by name, they cannot be found by traversing a symbol. In practice, around 80% of type information in a PDB is referenced by a symbol. That seems like a reasonable number. I don't really plan to do anything with this tool. It mostly just exists for informational purposes, and to confirm that we probably don't need to implement type reference tracking in LLD. We can continue to merge all types as we do today without wasting space. Reviewers: zturner, aganea Subscribers: mgorny, hiraditya, arphaman, jdoerfert, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D59620 llvm-svn: 356692 2019-03-21 19:02:34 +01:00			`TypeReferenceTracker.cpp`
[llvm-pdbdump] Dump MSF headers to YAML. This is the simplest possible patch to get some kind of YAML output. All it dumps is the MSF header fields so that in theory an empty MSF file could be reconstructed. Reviewed By: ruiu, majnemer Differential Revision: http://reviews.llvm.org/D20971 llvm-svn: 271939 2016-06-06 22:37:05 +02:00			`YAMLOutputStyle.cpp`
Rewrite llvm-pdbdump in terms of LLVMDebugInfoPDB. This makes llvm-pdbdump available on all platforms, although it will currently fail to create a dumper if there is no PDB reader implementation for the current platform. It implements dumping of compilands and children, which is less information than was previously available, but it has to be rewritten from scratch using the new set of interfaces, so the rest of the functionality will be added back in subsequent commits. llvm-svn: 228755 2015-02-10 23:43:25 +01:00			`)`