From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/24795] eu-unstrip doesn't recognize MIPS_DWARF as debug section
Date: Tue, 09 Jul 2019 21:54:00 -0000 [thread overview]
Message-ID: <bug-24795-10460-tZeg6i4571@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24795-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24795
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> ---
(In reply to Tom de Vries from comment #0)
> Consider the section header table of a hello world exec on debian 7 MIPS:
BTW. Isn't Debian 7 really old?
> This is with an old eu-strip (0.152), but I don't manage building from git
> for now,
See the README:
To build a git checkout do:
autoreconf -i -f && \
./configure --enable-maintainer-mode && \
make && make check
Please let us know what issues you are seeing.
> so atm I cannot say whether this is fixed on trunk or not.
It isn't. elfutils doesn't have a MIPS backend and so knows nothing about
special MIPS ELF constructs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-09 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 21:41 [Bug tools/24795] New: " vries at gcc dot gnu.org
2019-07-09 21:54 ` mark at klomp dot org [this message]
2019-07-09 22:08 ` [Bug tools/24795] " vries at gcc dot gnu.org
2019-07-10 10:41 ` mark at klomp dot org
2019-07-10 10:44 ` mark at klomp dot 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-24795-10460-tZeg6i4571@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).