diff options
| author | Tom Tromey <tom@tromey.com> | 2021-08-08 09:36:12 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2021-08-10 15:33:34 -0600 |
| commit | 2c1db96b6614b8a9d8907c41bb16984d9f41a376 (patch) | |
| tree | 4240a33b29125cfc45b991245db8c5c4263c5ab4 /gdb/arch-utils.c | |
| parent | 192786c72a36388dcf99e21b0335eca0977f3435 (diff) | |
| download | binutils-2c1db96b6614b8a9d8907c41bb16984d9f41a376.zip binutils-2c1db96b6614b8a9d8907c41bb16984d9f41a376.tar.gz binutils-2c1db96b6614b8a9d8907c41bb16984d9f41a376.tar.bz2 | |
Ignore .debug_types when reading .debug_aranges
I noticed that the fission-reread.exp test case can cause a complaint
when run with --target_board=cc-with-debug-names:
warning: Section .debug_aranges in [...]/fission-reread has duplicate debug_info_offset 0x0, ignoring .debug_aranges.
The bug here is that this executable has both .debug_info and
.debug_types, and both have a CU at offset 0x0. This triggers the
duplicate warning.
Because .debug_types doesn't provide any address ranges, these CUs can
be ignored. That is, this bug turns out to be another regression from
the info/types merger patch.
This patch fixes the problem by having this loop igore type units.
fission-reread.exp is updated to test for the bug.
Diffstat (limited to 'gdb/arch-utils.c')
0 files changed, 0 insertions, 0 deletions