From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Fix .gdb_index with Ada
Date: Wed, 28 Sep 2022 04:00:19 +0200 [thread overview]
Message-ID: <03994f80-2aa9-e30a-2cab-d458b402e148@suse.de> (raw)
In-Reply-To: <20220922202054.2773698-1-tromey@adacore.com>
On 9/22/22 22:20, Tom Tromey via Gdb-patches wrote:
> This series improves .gdb_index support for Ada, fixing a regression
> introduced by the DWARF reader rewrite.
>
> I regression tested this using the cc-with-gdb-index target board on
> x86-64 Fedora 34. There were no regressions, only improvements.
>
Hi,
I've tested this series with target board cc-with-gdb-index.
The only FAILs I found were:
...
$ grep ^FAIL: gdb.sum
FAIL: gdb.base/c-linkage-name.exp: print symada__cS before partial
symtab expansion
FAIL: gdb.dwarf2/dw2-zero-range.exp: ranges_sect=ranges: Zero address
complaint - relocated - psymtab
FAIL: gdb.dwarf2/dw2-zero-range.exp: ranges_sect=ranges: Zero address
complaint - unrelocated - psymtab
FAIL: gdb.dwarf2/dw2-zero-range.exp: ranges_sect=rnglists: Zero address
complaint - relocated - psymtab
FAIL: gdb.dwarf2/dw2-zero-range.exp: ranges_sect=rnglists: Zero address
complaint - unrelocated - psymtab
FAIL: gdb.python/py-symbol.exp: print (len (gdb.lookup_static_symbols
('rr')))
...
The FAILs from gdb.python/py-symbol.exp and
gdb.dwarf2/dw2-zero-range.exp are know, they also fail with target board
cc-with-debug-names.
The gdb.base/c-linkage-name.exp FAIL does look relevant to this series,
and probably was regressed by the same offending commit.
Doing:
...
diff --git a/gdb/dwarf2/index-write.c b/gdb/dwarf2/index-write.c
index ae05946e790..0268371ec2e 100644
--- a/gdb/dwarf2/index-write.c
+++ b/gdb/dwarf2/index-write.c
@@ -1167,7 +1167,6 @@ write_cooked_index (cooked_index_vector *table,
minimal symbols anyway, so including it in the index is
usually redundant -- and the cases where it would not be
redundant are rare and not worth supporting. */
- continue;
}
gdb_index_symbol_kind kind;
...
fixes the FAIL, so is this one of the "rare and not worth supporting"
cases you're referring to?
Thanks,
- Tom
next prev parent reply other threads:[~2022-09-28 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:20 Tom Tromey
2022-09-22 20:20 ` [PATCH 1/2] Improve Ada support in .gdb_index Tom Tromey
2022-09-22 20:20 ` [PATCH 2/2] Change .gdb_index de-duplication implementation Tom Tromey
2022-09-28 2:00 ` Tom de Vries [this message]
2022-10-11 19:59 ` [PATCH 0/2] Fix .gdb_index with Ada Tom Tromey
2022-10-13 20:40 ` Tom Tromey
2022-10-13 21:44 ` Tom de Vries
2022-10-14 13:24 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03994f80-2aa9-e30a-2cab-d458b402e148@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).