aboutsummaryrefslogtreecommitdiff
path: root/gdb/dwarf2/cu.h
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2022-04-21 07:28:56 -0600
committerTom Tromey <tromey@adacore.com>2022-04-29 13:16:44 -0600
commit446fcb446f57dbb33728c3dbd5f092bca3ba3547 (patch)
tree96b019204ce93ee7ab663b235543c80e5d946ac6 /gdb/dwarf2/cu.h
parent225170409b47bc96b62b2ecfcc0d9d5ae1ef8949 (diff)
downloadgdb-446fcb446f57dbb33728c3dbd5f092bca3ba3547.zip
gdb-446fcb446f57dbb33728c3dbd5f092bca3ba3547.tar.gz
gdb-446fcb446f57dbb33728c3dbd5f092bca3ba3547.tar.bz2
Fix .debug_names regression with new indexer
At AdaCore, we run the internal gdb test suite in several modes, including one using the .debug_names index. This caught a regression caused by the new DWARF indexer. First, the psymtabs-based .debug_names generator was completely wrong. However, to avoid making the rewrite series even bigger (fixing the writer will also require rewriting the .debug_names reader), it attempted to preserve the weirdness. However, this was not done properly. For example the old writer did this: - case STRUCT_DOMAIN: - return DW_TAG_structure_type; The new code, instead, simply preserves the actual DWARF tag -- but this makes future lookups fail, because the .debug_names reader only looks for DW_TAG_structure_type. This patch attempts to revert to the old behavior in the writer.
Diffstat (limited to 'gdb/dwarf2/cu.h')
0 files changed, 0 insertions, 0 deletions