File: pdbdump-write.test

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (20 lines) | stat: -rw-r--r-- 1,211 bytes parent folder | download | duplicates (28)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
; This testcase checks to make sure that we can write PDB files.  It
; works by first reading a known good PDB file and dumping the contents
; to YAML.  Then it tries to reconstruct as much of the original PDB as
; possible, although depending on what flags are specified when generating
; the YAML, the PDB might be missing data required for any standard tool
; to recognize it.  Finally, it dumps the same set of fields from the newly
; constructed PDB to YAML, and verifies that the YAML is the same as the
; original YAML generated from the good PDB.  Note that when doing the
; final comparison it must dump the original and the new pdb without any
; stream metadata, since the layout of the MSF file might be different
; (for example if we don't write the entire stream)
;
; RUN: llvm-pdbutil pdb2yaml -stream-metadata -stream-directory \
; RUN:   -pdb-stream -tpi-stream -module-syms %p/Inputs/empty.pdb > %t.1
; RUN: llvm-pdbutil yaml2pdb -pdb=%t.2 %t.1
; RUN: llvm-pdbutil pdb2yaml -pdb-stream -tpi-stream \
; RUN:   -module-syms -no-file-headers %p/Inputs/empty.pdb > %t.3
; RUN: llvm-pdbutil pdb2yaml -pdb-stream -tpi-stream \
; RUN:   -module-syms -no-file-headers %t.2 > %t.4
; RUN: diff %t.3 %t.4