From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/23370] run-next-cfi-self.sh doesn't handle compressed ELF sections
Date: Tue, 10 Jul 2018 17:48:00 -0000 [thread overview]
Message-ID: <bug-23370-10460-QhcTg3aynX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23370-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23370
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Martin Liska from comment #2)
> The suggested patch works for me as we in openSUSE have enabled compression
> of debug info section in gas for all targets.
Thanks for testing. Pushed to master.
commit b40001f67c0809e2fe8c7a78c2a5ac12026f23b4 (HEAD -> master)
Author: Mark Wielaard <mark@klomp.org>
Date: Thu Jul 5 16:24:57 2018 +0200
tests: Handle compressed sections in next_cfi testcase.
Some toolchains use compressed ELF sections by default.
This would make run-next-cfi-self.sh fail because it would try to
decode the compressed data. Fix by decompressing the section first.
https://sourceware.org/bugzilla/show_bug.cgi?id=23370
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:[~2018-07-10 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 14:12 [Bug general/23370] New: run-next-cfi-self.sh fails on armv7l mliska at suse dot cz
2018-07-05 14:21 ` [Bug general/23370] run-next-cfi-self.sh doesn't handle compressed ELF sections mark at klomp dot org
2018-07-10 13:12 ` mliska at suse dot cz
2018-07-10 17:48 ` 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-23370-10460-QhcTg3aynX@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).