diff options
author | Tom de Vries <tdevries@suse.de> | 2023-11-27 21:15:26 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2023-11-27 21:15:26 +0100 |
commit | f1b8ee6f2b4381bc46a0ad4c233b6eddc1e135b5 (patch) | |
tree | 58ca510a8f8ee934d9dd893c182b9a2b1143f831 /gdb/i387-tdep.h | |
parent | 0da23004a064e7149373b484fa671f2a2105ec9b (diff) | |
download | gdb-f1b8ee6f2b4381bc46a0ad4c233b6eddc1e135b5.zip gdb-f1b8ee6f2b4381bc46a0ad4c233b6eddc1e135b5.tar.gz gdb-f1b8ee6f2b4381bc46a0ad4c233b6eddc1e135b5.tar.bz2 |
[gdb/testsuite] Add boards/cc-with-index-cache.exp
We have a target board cc-with-gdb-index that uses the gdb-add-index script to
add a .gdb_index index to an exec.
There is however an alternative way of adding a .gdb_index: the index-cache.
Add a new target board cc-with-index-cache.
This is not superfluous for two reasons:
- there is functionality that gdb-add-index doesn't support, but the
index-cache does: the index-cache can add an index to an exec with a
.gnu_debugaltlink (note that when using the cc-with-gdb-index board this
case is quietly ignored), and
- using the index-cache is excercised in only a few test-cases, and having
this target board extends the test coverage to the entire test suite. This
is for instance relevant because the index-cache is written by a worker
thread in the background, so we can check more thoroughly for data races
(see PR symtab/30837).
Tested on x86_64-linux.
Shell script changes checked with shellcheck.
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/i387-tdep.h')
0 files changed, 0 insertions, 0 deletions