summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/help/TestHelp.py
diff options
context:
space:
mode:
authorDavid Blaikie <dblaikie@gmail.com>2016-03-24 18:37:08 +0000
committerDavid Blaikie <dblaikie@gmail.com>2016-03-24 18:37:08 +0000
commit0b214e4a2a2cc31f186f27e9e4a8417fca897e10 (patch)
treedc2f6d6b8fd45072f0f104790bdfc5506c239ccd /lldb/packages/Python/lldbsuite/test/help/TestHelp.py
parente8ae26fb3493ae6e054d65a50f578fe5003d6caf (diff)
downloadbcm5719-llvm-0b214e4a2a2cc31f186f27e9e4a8417fca897e10.tar.gz
bcm5719-llvm-0b214e4a2a2cc31f186f27e9e4a8417fca897e10.zip
[debuginfo] Include dwo_name in the split unit to improve dwp diagnostics
When multiple DWP files are merged together and duplicate DWO IDs are found it's currently difficult to give an actionable error message - the DW_AT_name of the CU could be provided, but might be identical (if the same source file is built into two different configurations), which doesn't help the user identify the problem. When no intermediate DWP files are generated, the path to the two DWO files could be provided - but is lost once the DWOs are merged into a DWP. So, include the name of the DWO (dwo_name) in the split file so that collissions involving a source CU from a DWP can be better diagnosed. (improvements to llvm-dwp using this to come shortly) llvm-svn: 264316
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/help/TestHelp.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud