From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29565] New: elfutils: support zstd for SHF_COMPRESSED debug sections
Date: Mon, 12 Sep 2022 03:36:00 +0000 [thread overview]
Message-ID: <bug-29565-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29565
Bug ID: 29565
Summary: elfutils: support zstd for SHF_COMPRESSED debug
sections
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: i at maskray dot me
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Related: PR29397 (binutils: support zstd for SHF_COMPRESSED debug sections),
PR29563 (gdb: support zstd for SHF_COMPRESSED debug sections).
At a glance, src/elfcompress.c and src/readelf.c need to support
ELFCOMPRESS_ZSTD
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-09-12 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 3:36 i at maskray dot me [this message]
2022-09-30 9:23 ` [Bug general/29565] " mliska at suse dot cz
2022-10-24 11:10 ` mliska at suse dot cz
2022-12-23 8:48 ` mliska at suse dot cz
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-29565-10460@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).