summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
diff options
context:
space:
mode:
authorMartin Storsjo <martin@martin.st>2018-11-27 09:20:55 +0000
committerMartin Storsjo <martin@martin.st>2018-11-27 09:20:55 +0000
commit3c046af5a931055470d23cceaaae3d9903dfe2a9 (patch)
tree15c92a66cc883fb262a38f13206f30e1fe679dca /lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
parentb0a9b75e2aa0c9123b0c1be02a05bd4f3b719555 (diff)
downloadbcm5719-llvm-3c046af5a931055470d23cceaaae3d9903dfe2a9.tar.gz
bcm5719-llvm-3c046af5a931055470d23cceaaae3d9903dfe2a9.zip
[COFF] Generate a codeview build id signature for MinGW even when not creating a PDB
GNU ld, which doesn't generate PDBs, can optionally generate a build id by passing the --build-id option. LLD's MinGW frontend knows about this option but ignores it, as I had falsely assumed that LLD already generated build IDs even in those cases. If debug info is requested and no PDB path is set, generate a build id signature as a hash of the binary itself. This allows associating a binary to a minidump, even if debug info isn't written in PDB form by the linker. Differential Revision: https://reviews.llvm.org/D54828 llvm-svn: 347645
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud