From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/28161] debugedit fails test against gcc git/binutils-2.37: [debugedit 5.0] testsuite: 17 19 21 failed
Date: Wed, 04 Aug 2021 09:44:58 +0000 [thread overview]
Message-ID: <bug-28161-13298-FdHUDKhfWN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28161-13298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28161
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
commit ae27211cbbfb63a0ad3c141cd1310d7f583ec40e
Author: Mark Wielaard <mark@klomp.org>
Date: Fri Jul 30 18:09:46 2021 +0200
tests: Handle zero directory entry in .debug_line DWARF5 debugedit.at
We were skipping the zero directory entry, because it was always
the same as the directory entry at position one. But that isn't
true anymore with gcc 11.2.1. There the zero dir entry is unique.
Fix the debugedit.at .debug_line testcases using DWARF5 to also
include dir entry zero.
Signed-off-by: Mark Wielaard <mark@klomp.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-08-04 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 20:56 [Bug debugedit/28161] New: " slyfox at inbox dot ru
2021-08-01 20:58 ` [Bug debugedit/28161] " slyfox at inbox dot ru
2021-08-01 21:08 ` mark at klomp dot org
2021-08-01 21:18 ` slyfox at inbox dot ru
2021-08-02 22:44 ` mark at klomp dot org
2021-08-03 22:07 ` slyfox at inbox dot ru
2021-08-04 9:44 ` mark at klomp dot org [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=bug-28161-13298-FdHUDKhfWN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=debugedit@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).