From: Tom Tromey <tromey@adacore.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>, Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH] Fix incorrect .gdb_index with new DWARF scanner
Date: Fri, 21 Oct 2022 10:13:07 -0600 [thread overview]
Message-ID: <87wn8tb1f0.fsf@tromey.com> (raw)
In-Reply-To: <47302e23-30af-d8ca-b1fb-28977110a72a@suse.de> (Tom de Vries via Gdb-patches's message of "Tue, 18 Oct 2022 15:41:53 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>> PR symtab/29694 points out a regression caused by the new DWARF
>> scanner when the cc-with-gdb-index target board is used.
[...]
Tom> Regression tested on openSUSE Tumbleweed x86_64 with native and
Tom> cc-with-gdb-index board, results looks good.
Tom> Patch LGTM.
Thank you. I'm going to check it in.
There's still one open regression for the new DWARF reader. I haven't
fully investigated it yet.
(There's also the TSan bug(s), but on my machine TSan reports a lot of
obviously untrue things, like captured_main being called from a signal
handler. So I haven't really looked at this at all.)
Tom
prev parent reply other threads:[~2022-10-21 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 19:41 Tom Tromey
2022-10-18 13:41 ` Tom de Vries
2022-10-21 16:13 ` Tom Tromey [this message]
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=87wn8tb1f0.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).