From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/26738] .debug_line reference above end of section
Date: Thu, 15 Oct 2020 16:39:23 +0000 [thread overview]
Message-ID: <bug-26738-11298-S9Gl9ETtNS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26738-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26738
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 Matthias Klose from comment #0)
> Created attachment 12902 [details]
> test case
>
> this is seen on mipsel-linux-gnu, not on other archs, and not on
> mips64el-linux-gnu. seen both with 0.13 and trunk.
I can replicate it with the provided reproducer.
But there is something odd with the .debug sections.
They all have an unknown section type: SHT_LOPROC+1e
And eu-readelf has trouble reading the debuginfo itself.
Do you happen to know whether mipsel-linux-gnu uses some special interpretation
of ELF/DWARF?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-15 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 15:56 [Bug default/26738] New: " doko at debian dot org
2020-10-15 15:57 ` [Bug default/26738] " doko at debian dot org
2020-10-15 16:39 ` mark at klomp dot org [this message]
2020-10-19 21:07 ` [Bug default/26738] .debug_line reference above end of section (mipsel) mark at klomp dot org
2021-03-02 13:20 ` vries at gcc dot gnu.org
2021-03-02 13:57 ` vries at gcc dot gnu.org
2021-03-04 8:18 ` vries at gcc dot gnu.org
2021-03-05 6:32 ` 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-26738-11298-S9Gl9ETtNS@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).