1ab58ae87SZachary Turner; This testcase checks to make sure that we can write PDB files. It 2ab58ae87SZachary Turner; works by first reading a known good PDB file and dumping the contents 3ab58ae87SZachary Turner; to YAML. Then it tries to reconstruct as much of the original PDB as 4ab58ae87SZachary Turner; possible, although depending on what flags are specified when generating 5ab58ae87SZachary Turner; the YAML, the PDB might be missing data required for any standard tool 6ab58ae87SZachary Turner; to recognize it. Finally, it dumps the same set of fields from the newly 7ab58ae87SZachary Turner; constructed PDB to YAML, and verifies that the YAML is the same as the 8faa554b2SZachary Turner; original YAML generated from the good PDB. Note that when doing the 9faa554b2SZachary Turner; final comparison it must dump the original and the new pdb without any 10faa554b2SZachary Turner; stream metadata, since the layout of the MSF file might be different 11faa554b2SZachary Turner; (for example if we don't write the entire stream) 12ab58ae87SZachary Turner; 13*bd336e44SZachary Turner; RUN: llvm-pdbutil pdb2yaml -stream-metadata -stream-directory \ 143eedd161SZachary Turner; RUN: -pdb-stream -tpi-stream -module-syms %p/Inputs/empty.pdb > %t.1 15*bd336e44SZachary Turner; RUN: llvm-pdbutil yaml2pdb -pdb=%t.2 %t.1 16*bd336e44SZachary Turner; RUN: llvm-pdbutil pdb2yaml -pdb-stream -tpi-stream \ 173eedd161SZachary Turner; RUN: -module-syms -no-file-headers %p/Inputs/empty.pdb > %t.3 18*bd336e44SZachary Turner; RUN: llvm-pdbutil pdb2yaml -pdb-stream -tpi-stream \ 193eedd161SZachary Turner; RUN: -module-syms -no-file-headers %t.2 > %t.4 20faa554b2SZachary Turner; RUN: diff %t.3 %t.4 21