diff options
| author | Tom Tromey <tromey@adacore.com> | 2022-04-13 11:21:20 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-02-24 11:46:53 -0700 |
| commit | 542a33e348a58e4a9ede20ce294b90d917e1e60c (patch) | |
| tree | 6ae8c92117c29d0ffb9c13fc99c810d9fe1fa8ab /gdb/testsuite/lib/gdb-python.exp | |
| parent | 71797f1221a95b2c8822e0137c301d31805d4964 (diff) | |
| download | gdb-542a33e348a58e4a9ede20ce294b90d917e1e60c.zip gdb-542a33e348a58e4a9ede20ce294b90d917e1e60c.tar.gz gdb-542a33e348a58e4a9ede20ce294b90d917e1e60c.tar.bz2 | |
Only use the per-BFD object to write a DWARF index
The DWARF index does not need access to the objfile or per-objfile
objects when writing -- it's entirely based on the objfile-independent
per-BFD data.
This patch implements this idea by changing the entire API to only be
passed the per-BFD object. This simplifies some lifetime reasoning
for the next patch.
This patch removes some code that ensures that the BFD came from a
file. It seems to me that checking for the existence of a build-id is
good enough for the index cache.
Diffstat (limited to 'gdb/testsuite/lib/gdb-python.exp')
0 files changed, 0 insertions, 0 deletions