From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Mark Wielaard <mark@klomp.org>
Cc: debugedit@sourceware.org, Vitaly Chikunov <vt@altlinux.org>
Subject: Re: [PATCH] tests: fix for toolchains producing compressed debug sections
Date: Tue, 23 Mar 2021 17:28:52 +0300 [thread overview]
Message-ID: <20210323142852.GA15238@altlinux.org> (raw)
In-Reply-To: <c64e039e6b97746baed0bbd666ba309cc1586dfc.camel@klomp.org>
On Tue, Mar 23, 2021 at 03:20:12PM +0100, Mark Wielaard wrote:
> On Mon, 2021-03-22 at 20:00 +0000, Dmitry V. Levin wrote:
> > When toolchain produces compressed debug sections by default,
> > quite a few debugedit tests fail because of unexpected
> > "debugedit: ./foo.o: DWARF version 0 unhandled" error diagnostic messages:
> > 3: debugedit .debug_str objects DWARF4 FAILED (debugedit.at:97)
> > 4: debugedit .debug_str/line_str objects DWARF5 FAILED (debugedit.at:129)
> > 9: debugedit .debug_info objects FAILED (debugedit.at:291)
> > 12: debugedit .debug_types objects FAILED (debugedit.at:370)
> > 15: debugedit .debug_line objects DWARF4 FAILED (debugedit.at:460)
> > 16: debugedit .debug_line objects DWARF5 FAILED (debugedit.at:484)
> > 21: debugedit .debug_macro objects FAILED (debugedit.at:598)
> >
> > Fix this by instructing gcc not to produce compressed debug sections
> > in object files prepared for debugedit tests.
> >
> > * tests/debugedit.at: Add "-gz=none" to "gcc -g3" invocations.
>
> Yes, that is a good workaround for now.
> But we should at least give a good error message.
> And ideally just handle compressed debug ELF sections (But then the
> question is how? Do we always simply decompress, do we require an
> explicit command line option? Do we simply recompress when done?)
>
> I filed https://sourceware.org/bugzilla/show_bug.cgi?id=27636
>
> > Co-authored-by: Vitaly Chikunov <vt@altlinux.org>
>
> And Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>, I assume?
Yes, Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
--
ldv
next prev parent reply other threads:[~2021-03-23 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 20:00 Dmitry V. Levin
2021-03-23 14:20 ` Mark Wielaard
2021-03-23 14:28 ` Dmitry V. Levin [this message]
2021-03-23 15:05 ` Mark Wielaard
2021-03-24 23:45 ` Dmitry V. Levin
2021-03-25 23:12 ` Mark Wielaard
2021-03-28 0:46 ` Dmitry V. Levin
2021-03-28 14:01 ` Mark Wielaard
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=20210323142852.GA15238@altlinux.org \
--to=ldv@altlinux.org \
--cc=debugedit@sourceware.org \
--cc=mark@klomp.org \
--cc=vt@altlinux.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).