diff options
| author | Tom Tromey <tom@tromey.com> | 2021-05-28 16:20:03 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2021-07-05 11:57:14 -0600 |
| commit | b5b44b5df07883e9dd81860ab49e08400727b70d (patch) | |
| tree | 45058b793fef7f410e979550f35502cad0a56fae /gdb/gdb_regex.c | |
| parent | b6aeb717a8bdaa9cc348ec88a5fdf059e1337580 (diff) | |
| download | gdb-b5b44b5df07883e9dd81860ab49e08400727b70d.zip gdb-b5b44b5df07883e9dd81860ab49e08400727b70d.tar.gz gdb-b5b44b5df07883e9dd81860ab49e08400727b70d.tar.bz2 | |
Fix oddity in write_gdbindex
My recent patch to unify CUs and TUs introduced an oddity in
write_gdbindex. Here, we pass 'i' to recursively_write_psymbols, but
we must instead pass 'counter', to handle the situation where a TU is
mixed in with the CUs.
I am not sure a test case for this is possible. I think it can only
happen when using DWARF 5, where a TU appears in .debug_info.
However, this situation is already not handled correctly by
.gdb_index. I filed a bug about this.
Diffstat (limited to 'gdb/gdb_regex.c')
0 files changed, 0 insertions, 0 deletions