diff options
author | Tom de Vries <tdevries@suse.de> | 2021-07-14 11:37:19 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2021-07-14 11:37:19 +0200 |
commit | be36c6e3374821fe5699556bbfa2280e3a4696df (patch) | |
tree | e09ee12055e325b11b3569badf38ecc2deb9e36d /binutils/dwarf.c | |
parent | 90d7916ac136613b8118f6429c3436664a700a2e (diff) | |
download | gdb-be36c6e3374821fe5699556bbfa2280e3a4696df.zip gdb-be36c6e3374821fe5699556bbfa2280e3a4696df.tar.gz gdb-be36c6e3374821fe5699556bbfa2280e3a4696df.tar.bz2 |
[gdb/testsuite] Fix gdb.base/gold-gdb-index.exp
When running test-case gdb.base/gold-gdb-index.exp on openSUSE Tumbleweed,
I run into:
...
FAIL: gdb.base/gold-gdb-index.exp: maint info symtabs
...
This is due to a dummy .gdb_index:
...
Contents of the .gdb_index section:
Version 7
CU table:
TU table:
Address table:
Symbol table:
...
The dummy .gdb_index is ignored when loading the symbols, and instead partial
symbols are used. Consequently, we get the same result as if we'd removed
-Wl,--gdb-index from the compilation.
Presumably, gold fails to generate a proper .gdb_index because it lacks
DWARF5 support.
Anyway, without a proper .gdb_index we can't test the gdb behaviour we're
trying to excercise. Fix this by detecting whether we actually used a
.gdb_index for symbol loading.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2021-07-14 Tom de Vries <tdevries@suse.de>
* lib/gdb.exp (have_index): New proc.
* gdb.base/gold-gdb-index.exp: Use have_index.
Diffstat (limited to 'binutils/dwarf.c')
0 files changed, 0 insertions, 0 deletions