#symbolication #tag-production #symbolic #debuginfo #dwarf


A library to inspect and load DWARF debugging information from binaries, such as Mach-O or ELF

112 stable releases (11 major)

12.8.0 Dec 1, 2023
12.7.1 Nov 29, 2023
12.5.0 Oct 24, 2023
12.3.0 Jul 19, 2023
1.1.5 Dec 2, 2017

#778 in Debugging

Download history 1176/week @ 2023-11-03 1361/week @ 2023-11-10 1764/week @ 2023-11-17 1735/week @ 2023-11-24 1821/week @ 2023-12-01 1648/week @ 2023-12-08 1512/week @ 2023-12-15 1072/week @ 2023-12-22 1122/week @ 2023-12-29 1782/week @ 2024-01-05 2423/week @ 2024-01-12 3075/week @ 2024-01-19 2858/week @ 2024-01-26 6341/week @ 2024-02-02 7336/week @ 2024-02-09 4250/week @ 2024-02-16

21,316 downloads per month
Used in 21 crates (11 directly)

MIT license

13K SLoC

Abstractions for dealing with object files and debug information.

This module defines the Object type, which is an abstraction over various object file formats used in different platforms. Also, since executables on MacOS might contain multiple object files (called a "Fat MachO"), there is an Archive type, that provides a uniform interface with access to an objects iterator in all platforms.

Most processing of object files will happen on the Object type or its concrete implementation for one platform. To allow abstraction over this, there is the ObjectLike trait. It defines common attributes and gives access to a DebugSession, which can be used to perform more stateful handling of debug information.

See Object for the full API, or use one of the modules for direct access to the platform-dependent data.


The functionality of symbolic::debuginfo is conceptionally similar to the object crate. However, there are key differences that warranted a separate implementation:

  • object has a stronger focus on executable formats, while symbolic focusses on debugging information. This is why symbolic also includes a variant for PDBs and Breakpad objects, where object instead has a WASM variant.
  • object contains far more generic access to the data within objects at the cost of performance. symbolic tries to optimize for debugging scenarios at the cost of generic usage.
  • symbolic contains an abstraction for multi-object files (Archive), which is not easily possible in object due to the use of lifetimes on the object::Object trait.


~80K SLoC