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/31689] [gdb/symtab] PR gas/29517 workaround, dwarf2 case
Date: Thu, 02 May 2024 07:34:28 +0000 [thread overview]
Message-ID: <bug-31689-4717-gY61igYEne@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31689-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31689
--- 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=5ce0e02478cc79a260c7e29822450284a32b9b12
commit 5ce0e02478cc79a260c7e29822450284a32b9b12
Author: Tom de Vries <tdevries@suse.de>
Date: Thu May 2 09:34:46 2024 +0200
[gdb/symtab] Work around PR gas/29517, dwarf2 case
In commit 1d45d90934b ("[gdb/symtab] Work around PR gas/29517") we added a
workaround for PR gas/29517.
The problem is present in gas version 2.39, and fixed in 2.40, so the
workaround is only active for gas version == 2.39.
However, the problem in gas is only fixed for dwarf version >= 3, which
supports DW_TAG_unspecified_type.
Fix this by also activating the workaround for dwarf version == 2.
Tested on x86_64-linux.
Approved-by: Kevin Buettner <kevinb@redhat.com>
PR symtab/31689
https://sourceware.org/bugzilla/show_bug.cgi?id=31689
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-05-02 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 13:14 [Bug symtab/31689] New: " vries at gcc dot gnu.org
2024-05-01 13:21 ` [Bug symtab/31689] " vries at gcc dot gnu.org
2024-05-01 13:22 ` vries at gcc dot gnu.org
2024-05-01 14:46 ` vries at gcc dot gnu.org
2024-05-02 7:34 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-02 7:35 ` 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-31689-4717-gY61igYEne@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: 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).