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] gdb: support zstd for SHF_COMPRESSED debug sections Date: Fri, 09 Sep 2022 20:11:00 +0000 [thread overview] Message-ID: <bug-29563-4717-EXmQUXcAZ9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29563-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29563 --- Comment #1 from Fangrui Song <i at maskray dot me> --- llvm-project has some components supporting zstd now. Some instructions for developers who want to test gdb's support: git clone https://github.com/facebook/zstd cd zstd cmake -GNinja -Hbuild/cmake -Bout/release -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/tmp/opt/zstd make -j 8 install # See https://llvm.org/docs/GettingStarted.html # Example: cmake -GNinja -Sllvm -Bout/release -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS='clang;lld' -DLLVM_ENABLE_ZSTD=FORCE_ON -DCMAKE_PREFIX_PATH=/tmp/opt/zstd; ninja -C out/release llvm-objcopy clang lld You can create zstd output with out/release/bin/llvm-objcopy --compress-debug-sections=zstd a.out a.out.zstd or out/release/bin/clang -fuse-ld=lld -gz=zstd a.o b.o ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-09 20:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-09 20:02 [Bug gdb/29563] New: " i at maskray dot me 2022-09-09 20:11 ` i at maskray dot me [this message] 2022-09-09 20:18 ` [Bug gdb/29563] " 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-EXmQUXcAZ9@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).