public inbox for
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <>
Subject: [Bug debugedit/27636] New: Debugedit doesn't handle compressed debug ELF sections
Date: Tue, 23 Mar 2021 14:19:55 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 27636
           Summary: Debugedit doesn't handle compressed debug ELF sections
           Product: debugedit
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debugedit
          Assignee: unassigned at sourceware dot org
          Reporter: mark at klomp dot org
                CC: debugedit at sourceware dot org
  Target Milestone: ---

When seeing compressed debug ELF sections debugedit gets confused:

debugedit: ./foo.o: DWARF version 0 unhandled

This is a somewhat useless error message.

We should at least detect SHF_COMPRESSED (or .zdebug...) and explicitly say we
don't handle compressed sections.

If we do decide to handle compressed sections there are a couple of ways:
- Do we simply always uncompress and leave it that way?
- Do we recompress afterwards?
- Do we require an explicit flag to (de/re)compress?

You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-03-23 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 14:19 mark at klomp dot org [this message]
2023-12-05 14:14 ` [Bug debugedit/27636] " mark at klomp dot org
2023-12-11 13:59 ` mark at klomp dot org
2023-12-11 14:01 ` mark at klomp dot org
2024-06-27  7:56 ` at gmail dot com

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).