diff options
| author | Tom de Vries <tdevries@suse.de> | 2020-11-02 11:25:38 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2020-11-02 11:25:38 +0100 |
| commit | ab8f783d7ad51895d961b1bc6b82abcd8118e9a1 (patch) | |
| tree | 3b61bb7a6daec3c324c7de0f81e0cf5236ad39b2 /gdb/break-catch-syscall.c | |
| parent | e1f57067b162cba9f39e087726c7a2f2cfaae96f (diff) | |
| download | gdb-ab8f783d7ad51895d961b1bc6b82abcd8118e9a1.zip gdb-ab8f783d7ad51895d961b1bc6b82abcd8118e9a1.tar.gz gdb-ab8f783d7ad51895d961b1bc6b82abcd8118e9a1.tar.bz2 | |
[gdb/testsuite] Remove .debug_line.dwo from gdb.dwarf2/fission-multi-cu.S
Consider test-case gdb.dwarf2/fission-multi-cu.exp. It produces an executable
fission-multi-cu and a dwo file fission-multi-cu.dwo.
The file fission-multi-cu.dwo contains a .debug_line.dwo section, which
according to the DWARF v5 standard is a "specialized line number table" for
type units in the .debug_info.dwo section, and contains only the directory and
filename lists.
When reading the actual .debug_line.dwo section using readelf -w, we get:
...
The Directory Table is empty.
The File Name Table is empty.
No Line Number Statements.
...
So, the section does not contain any actual information. Furthermore, no
information is required because the .debug_line.dwo section does not contain
any type units.
This is confirmed by:
- re-doing the commands listed at the start of fission-multi-cu.S, which were
used as starting point for fission-multi-cu.S, and
- compiling the fission-multi-cu{1,2}.c files with clang -flto -g -gsplit-dwarf
In both cases, no .debug_line.dwo section is generated.
Remove the .debug_line.dwo section, to make it fit how split dwarf is actually
generated by clang.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2020-11-02 Tom de Vries <tdevries@suse.de>
* gdb.dwarf2/fission-multi-cu.S: Remove .debug_line.dwo section.
Diffstat (limited to 'gdb/break-catch-syscall.c')
0 files changed, 0 insertions, 0 deletions