Update DWZ to version 0.13 plus recent bugfixes

[fwyzard]

When building CMSSW 11.0.0 with debug symbols I got

dwz: libRecoEgammaEgammaIsolationAlgos.so: Unknown DWARF DW_OP_253
dwz: plugintestGEMRecHittestGEMRecHitAnalyzer.so: Unknown DWARF DW_OP_253

Updating DWZ to version 0.13 is supposed to fix this issue.

[cmsbuild]

A new Pull Request was created by @fwyzard (Andrea Bocci) for branch IB/CMSSW_11_1_X/master.

@cmsbuild, @smuzaffar, @mrodozov, @tulamor can you please review it and eventually sign? Thanks.
cms-bot commands are listed here

[fwyzard]

For the most recent bug fixes, see https://sourceware.org/git/?p=dwz.git;a=shortlog;h=refs/heads/dwz-0.13-branch .

[fwyzard]

@cmsbuild, please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/4343/console Started: 2020/01/24 11:03

[cmsbuild]

+1
Tested at: 5f1423a
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5872ff/4343/summary.html
CMSSW: CMSSW_11_1_X_2020-01-23-2300
SCRAM_ARCH: slc7_amd64_gcc820

[cmsbuild]

Comparison job queued.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5872ff/4343/summary.html

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 34
• DQMHistoTests: Total histograms compared: 2697090
• DQMHistoTests: Total failures: 1
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2696743
• DQMHistoTests: Total skipped: 346
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
• Checked 147 log files, 16 edm output root files, 34 DQM output files

[smuzaffar]

+externals

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_11_1_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)