From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/28599] 5.0 test failures on mips64el-linux-gnu
Date: Wed, 17 Nov 2021 18:37:24 +0000 [thread overview]
Message-ID: <bug-28599-13298-L4DST9xhGH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28599-13298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28599
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
I am not sure what is going wrong here.
The is some special case code for MIPS in tools/debugedit.c:
case SHT_MIPS_DWARF:
/* According to the specification, all MIPS .debug_* sections are
marked with ELF type SHT_MIPS_DWARF. As SHT_MIPS_DWARF is from
processor-specific range, we have to check that we're actually
dealing with MIPS ELF file before handling such sections. */
if (dso->ehdr.e_machine != EM_MIPS
&& dso->ehdr.e_machine != EM_MIPS_RS3_LE) {
break;
}
Maybe that needs updating for mips64?
There also is no specific handling of MIPS relocations in relbuf_setup.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-11-17 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 15:50 [Bug debugedit/28599] New: " doko at debian dot org
2021-11-17 15:50 ` [Bug debugedit/28599] " doko at debian dot org
2021-11-17 18:37 ` 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-28599-13298-L4DST9xhGH@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).