public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29563] New: gdb: support zstd for SHF_COMPRESSED debug sections Date: Fri, 09 Sep 2022 20:02:10 +0000 [thread overview] Message-ID: <bug-29563-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29563 Bug ID: 29563 Summary: gdb: support zstd for SHF_COMPRESSED debug sections Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: i at maskray dot me Target Milestone: --- Zstandard is a "universal" compression algorithm which scales from low-ratio-very-fast to high-ratio-pretty-slow. The generic-abi proposal https://groups.google.com/g/generic-abi/c/satyPkuMisk ("Add new ch_type value: ELFCOMPRESS_ZSTD") has been approved. See https://sourceware.org/bugzilla/show_bug.cgi?id=29397 for binutils feature request. gdb will need to support SHF_COMPRESSED (ch_type=ELFCOMPRESS_ZSTD) .debug_* sections in executables, shared objects, and (split DWARF) .dwo files. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-09 20:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-09 20:02 i at maskray dot me [this message] 2022-09-09 20:11 ` [Bug gdb/29563] " i at maskray dot me 2022-09-09 20:18 ` dblaikie at gmail dot com 2022-09-10 0:07 ` sam at gentoo dot org 2022-09-10 14:58 ` guillaume at morinfr dot org 2022-09-11 15:12 ` ssbssa at sourceware dot org 2022-09-19 4:05 ` i at maskray dot me 2022-09-19 4:24 ` i at maskray dot me 2022-09-27 2:54 ` i at maskray dot me 2022-09-27 2:55 ` i at maskray dot me
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-29563-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).