diff options
author | Zachary Turner <zturner@google.com> | 2018-03-13 17:46:06 +0000 |
---|---|---|
committer | Zachary Turner <zturner@google.com> | 2018-03-13 17:46:06 +0000 |
commit | 679aeadda116f1d87ba65fd524f5b901afbeeafb (patch) | |
tree | c4170a3e925a42daff933862501ae140e4b260be /lldb/packages/Python/lldbsuite/test/source-manager/TestSourceManager.py | |
parent | e5f72dd5e1b14814c1fbb0a10cbf02222782e5bd (diff) | |
download | bcm5719-llvm-679aeadda116f1d87ba65fd524f5b901afbeeafb.tar.gz bcm5719-llvm-679aeadda116f1d87ba65fd524f5b901afbeeafb.zip |
[PDB] Support dumping injected sources via the DIA reader.
Injected sources are basically a way to add actual source file content
to your PDB. Presumably you could use this for shipping your source code
with your debug information, but in practice I can only find this being
used for embedding natvis files inside of PDBs.
In order to effectively test LLVM's natvis file injection, we need a way
to dump the injected sources of a PDB in a way that is authoritative
(i.e. based on Microsoft's understanding of the PDB format, and not
LLVM's). To this end, I've added support for dumping injected sources
via DIA. I made a PDB file that used the /natvis option to generate a
test case.
Differential Revision: https://reviews.llvm.org/D44405
llvm-svn: 327428
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/source-manager/TestSourceManager.py')
0 files changed, 0 insertions, 0 deletions