public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/25969] Ignoring .debug_aranges with clang .debug_names Date: Wed, 06 Dec 2023 09:29:21 +0000 [thread overview] Message-ID: <bug-25969-4717-JT5N2qyAjE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25969-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25969 --- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b17ef9dcd8d16eedf4e60565cd7701698b5a0b6b commit b17ef9dcd8d16eedf4e60565cd7701698b5a0b6b Author: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> Date: Wed Dec 6 10:29:17 2023 +0100 [gdb/symtab] Redo "Fix assert in set_length" This reverts commit 1c04f72368c ("[gdb/symtab] Fix assert in set_length"), due to a regression reported in PR29572, and implements a different fix for PR29453. The fix is to not use the CU table in a .debug_names section to construct all_units, but instead use create_all_units, and then verify the CU table from .debug_names. This also fixes PR25969, so remove the KFAIL. Approved-By: Tom Tromey <tom@tromey.com> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29572 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=25969 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-06 9:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 9:10 [Bug symtab/25969] New: " vries at gcc dot gnu.org 2020-05-11 9:41 ` [Bug symtab/25969] " vries at gcc dot gnu.org 2020-09-22 6:18 ` sourav0311 at gmail dot com 2023-12-05 21:04 ` tromey at sourceware dot org 2023-12-06 9:29 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-06 9:36 ` vries at gcc dot gnu.org
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=bug-25969-4717-JT5N2qyAjE@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).