diff options
| author | Mark Williams <mark@myosotissp.com> | 2020-04-28 16:12:45 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2020-04-28 16:12:45 +0200 |
| commit | 770479f223ecd1920dd3cc683b05b24af25c4613 (patch) | |
| tree | aeae1890889747e08b165d86c2230886a47298d7 /gdb/python/py-cmd.c | |
| parent | 1b95cdb76caca1b7a9ecf9324acf23139f11f7d1 (diff) | |
| download | binutils-770479f223ecd1920dd3cc683b05b24af25c4613.zip binutils-770479f223ecd1920dd3cc683b05b24af25c4613.tar.gz binutils-770479f223ecd1920dd3cc683b05b24af25c4613.tar.bz2 | |
gdb: Fix toplevel types with -fdebug-types-section
When debugging a program compiled with -fdebug-types-section,
only the first top-level type in each file is visible to gdb.
The problem was caused by moving the assignment to list_in_scope
from process_full_comp_unit and process_full_type_unit to
start_symtab. This was fine for process_full_comp_unit, because
symtabs and comp units are one-to-one. But there can be many type
units per symtab (one for each type), and we only call start_symtab
for the first one. This adds the necessary assignments on the paths
where start_symtab is not called.
gdb/Changelog:
2020-04-28 Mark Williams <mark@myosotissp.com>
PR gdb/24480
* dwarf2read.c: Add missing assingments to list_in_scope when
start_symtab was already called.
gdb/testsuite/Changelog:
2020-04-28 Mark Williams <mark@myosotissp.com>
PR gdb/24480
* dw4-toplevel-types.exp: Test for top level types.
* dw4-toplevel-types.cc: Test for top level types.
Diffstat (limited to 'gdb/python/py-cmd.c')
0 files changed, 0 insertions, 0 deletions