Installer dwarfutils avec Homebrew, apt, zypper, Nix

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• dwarfdump

Historique du projet

The libdwarf project page says the DWARF debugging information format was developed by a committee, then known as PLSIG, starting around 1991. SGI became involved around 1991 and developed libdwarf and dwarfdump for SGI internal use and IRIX developer tools.

According to the same page, from around 1993 dwarfdump and libdwarf shipped with every SGI MIPS/IRIX C compiler release as an executable and archive library. SGI agreed to open-source libdwarf in 1994 and dwarfdump in 1999.

The project later moved through SourceForge-era public hosting to GitHub. The project page says source was available via SourceForge git from March 2011, and that beginning 14 May 2021 the GitHub repository became the reference source with SourceForge no longer current.

Modern libdwarf focuses on portable access to DWARF2 through DWARF5 data, robust handling of corrupted DWARF, and build support via configure, CMake, and Meson. The README states that DWARF6 support will be added when the standard is released.

Historique d'adoption

The DWARF standard site describes DWARF as widely used on Unix, Linux, other operating systems, and stand-alone environments. That broad standard adoption gives libdwarf and dwarfdump enduring relevance even when the utilities themselves are niche.

The input metadata lists packages across Homebrew, Debian, Ubuntu, Nix, and zypper, reflecting its role as a distribution-level toolchain utility rather than an end-user application. The project page also highlights CI across Linux, FreeBSD, macOS, and Windows msys2 and testing against many corrupted objects.

Modes d'utilisation

dwarfdump prints DWARF2, DWARF3, DWARF4, and some DWARF5 data from object files in readable form. libdwarf provides C/C++ APIs for reading DWARF sections, while libdwarfp offers a limited producer API for creating DWARF data.

Typical users are compiler and debugger implementers, build-system and distribution maintainers, binary-analysis developers, and anyone debugging problems in generated debug information.

Pourquoi les passionnés de paquets s'y intéressent

dwarfutils is package-nerd significant because debug information is invisible until it breaks, then it is essential. Having dwarfdump available from a package manager gives maintainers a standard diagnostic tool for compiler output, stripped/split debug files, compressed sections, malformed objects, and DWARF version transitions.

Its history also ties modern open-source packaging to older proprietary Unix toolchains: SGI-originated debug tooling became portable free software, then continued evolving alongside ELF, Mach-O, PE object helpers, DWARF5, fuzzing, and semantic versioning.

Chronologie

• 1991: The DWARF format effort and SGI involvement begin, according to the libdwarf project page.
• 1993: dwarfdump and libdwarf begin shipping with SGI MIPS/IRIX C compiler releases.
• 1994: SGI agrees to open-source libdwarf.
• 1999: SGI agrees to open-source dwarfdump.
• 2011: libdwarf source becomes available via SourceForge git.
• 2017: DWARF Version 5 is released, according to the libdwarf project page.
• 2021: GitHub becomes the reference source; libdwarf transitions to semantic versioning.
• 2026: The README lists libdwarf 2.3.1 released on 4 March 2026.

Related projects

• DWARF Debugging Information Format is the standard that libdwarf and dwarfdump implement.
• Compiler and debugger ecosystems such as GCC, LLVM/Clang, GDB, LLDB, ELF, Mach-O, PE, split DWARF, and compressed debug sections are adjacent to the package's core use.
• The libdwarf project page also points to readelfobj, readobjmacho, readobjpe, object_detector, regression tests, and tsearch support code as related project resources.

Sources

• https://www.prevanders.net/dwarf.html
• https://raw.githubusercontent.com/davea42/libdwarf-code/main/README.md
• https://dwarfstd.org/
• https://api.github.com/repos/davea42/libdwarf-code