From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdb/symtab] Redo "Fix assert in set_length"
Date: Wed, 6 Dec 2023 10:34:44 +0100 [thread overview]
Message-ID: <b6831549-1710-4709-aa6e-89a93f078bbf@suse.de> (raw)
In-Reply-To: <87il5cjrgl.fsf@tromey.com>
On 12/5/23 21:59, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Tom> Hi,
> Tom> This reverts commit 1c04f72368c ("[gdb/symtab] Fix assert in set_length"), due
> Tom> to a regression reported in PR29572, and implements a different fix for PR29453.
>
> Tom> The fix is to not use the CU table in a .debug_names section to construct
> Tom> all_comp_units, but instead use create_all_comp_units, and then verify the CU
> Tom> table from .debug_names. This also fixes PR25969, so remove the KFAIL.
>
> Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29572
> Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=25969
>
> Tom> Any comments?
>
> I've come around on this patch and I think you should check it in.
>
> My main concern was the time cost, but you showed that this isn't
> important; and anyway gdb is probably going to map these sections and do
> more stuff with them later anyhow.
>
> So, I think you should check this in.
>
The patch no longer applied cleanly, so I've updated it.
Also I came across a finalize_all_units call in dwarf2_read_debug_names
that was no longer necessary, so I've removed that one.
Reposted here (
https://sourceware.org/pipermail/gdb-patches/2023-December/204835.html )
and committed.
Thanks,
- Tom
> Approved-By: Tom Tromey <tom@tromey.com>
>
> Tom
prev parent reply other threads:[~2023-12-06 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:00 Tom de Vries
2022-09-23 13:45 ` Tom Tromey
2022-09-27 12:44 ` Tom de Vries
2023-12-05 20:59 ` Tom Tromey
2023-12-06 9:34 ` Tom de Vries [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=b6831549-1710-4709-aa6e-89a93f078bbf@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).