26 releases

0.4.3 Aug 18, 2023
0.4.2 Jun 26, 2023
0.4.1 Apr 14, 2023
0.4.0 Oct 20, 2022
0.1.0 Dec 11, 2016

#28 in Debugging

Download history 154568/week @ 2023-11-21 172542/week @ 2023-11-28 160367/week @ 2023-12-05 156970/week @ 2023-12-12 131328/week @ 2023-12-19 69372/week @ 2023-12-26 150023/week @ 2024-01-02 166853/week @ 2024-01-09 197421/week @ 2024-01-16 189719/week @ 2024-01-23 185389/week @ 2024-01-30 193573/week @ 2024-02-06 191692/week @ 2024-02-13 214921/week @ 2024-02-20 218326/week @ 2024-02-27 163528/week @ 2024-03-05

826,894 downloads per month
Used in 744 crates (24 directly)

MIT/Apache

460KB
10K SLoC

cpp_demangle: a C++ linker symbol demangler

Build Status

This crate can parse a C++ “mangled” linker symbol name into a Rust value describing what the name refers to: a variable, a function, a virtual table, etc. The description type implements Display, producing human-readable text describing the mangled name. Debuggers and profilers can use this crate to provide more meaningful output.

C++ requires the compiler to choose names for linker symbols consistently across compilation units, so that two compilation units that have seen the same declarations can pair up definitions in one unit with references in another. Almost all platforms other than Microsoft Windows follow the Itanium C++ ABI's rules for this.

For example, suppose a C++ compilation unit has the definition:

namespace space {
  int foo(int x, int y) { return x+y; }
}

The Itanium C++ ABI specifies that the linker symbol for that function must be named _ZN5space3fooEii. This crate can parse that name into a Rust value representing its structure. Formatting the value with the format! macro or the std::string::ToString::to_string trait method yields the string space::foo(int, int), which is more meaningful to the C++ developer.

Usage

Add cpp_demangle to your crate's Cargo.toml:

[dependencies]
cpp_demangle = "0.4.3"

And then demangle some C++ symbols!

extern crate cpp_demangle;
use cpp_demangle::Symbol;
use std::string::ToString;

let mangled = b"_ZN5space3fooEibc";

let sym = Symbol::new(&mangled[..])
    .expect("Could not parse mangled symbol!");

let demangled = sym.to_string();
assert_eq!(demangled, "space::foo(int, bool, char)");

no_std Support

cpp_demangle may be configured for working in no_std environments that still have allocation support via the alloc crate. This is nightly rust only, at the moment, since the alloc crate's collections aren't stabilized.

Disable the "std" feature, and enable the "alloc" feature:

[dependencies]
cpp_demangle = {
  version = "0.4.3",
  default-features = false,
  features = ["alloc"]
}

Documentation

Documentation on docs.rs

Example programs:

  • A c++filt clone.

    Install it locally with this command:

    cargo install cpp_demangle --example cppfilt
    

Implementation Status

Work is ongoing. While cpp_demangle can parse every mangled symbol in libiberty's demangler's test suite (the canonical Itanium C++ symbol demangler used by GNU tools such as c++filt), it does not format all of them character-for-character identically. I'm working on fixing that ;)

Despite that, I believe cpp_demangle is fairly robust. I've been running AFL on cpp_demangle overnight and it hasn't found any panics for a long time now (and never found any crashes -- thanks Rust!).

License

Licensed under either of

at your option.

Contribution

See CONTRIBUTING.md for hacking.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~0–1.5MB
~11K SLoC