summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/value/main.c
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2018-03-07 18:13:41 +0000
committerZachary Turner <zturner@google.com>2018-03-07 18:13:41 +0000
commit69f3347b561a963b0f2d164cf143af63c030cf97 (patch)
treeec71fca8090177ddf6ca7c8b7de0a8e2936b7a18 /lldb/packages/Python/lldbsuite/test/python_api/value/main.c
parentc0311fe19b1fb6516d9eae3e96753951366e1ece (diff)
downloadbcm5719-llvm-69f3347b561a963b0f2d164cf143af63c030cf97.tar.gz
bcm5719-llvm-69f3347b561a963b0f2d164cf143af63c030cf97.zip
Write a hash of the executable into the PE timestamp fields.
Windows tools treats the timestamp fields as sort of a build id, using it to archive executables on a symbol server, as well as for matching executables to PDBs. We were writing 0 for these fields, which would cause symbol servers to break as they are indexed in the symbol server based on this value. Although the field is called timestamp, it can really be any value that is unique per build, so to support reproducible builds we use a hash of the executable here. Differential Revision: https://reviews.llvm.org/D43978 llvm-svn: 326920
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/main.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud