dwarf2sources(1)

💖 dwarf2sources 💖

okay bestie, come sit with me because today we're talking about dwarf2sources from the dwarf2sources(1) manual, section 1, and it's genuinely such a useful little gremlin. its whole job? list the source files for a given binary. that's it. that's the gig. ✨

---

🌸 NAME 🌸

dwarf2sources — literally just: list the source files for a given binary. iconic behaviour, no notes. 👑

---

🦋 SYNOPSIS 🦋

dwarf2sources [-o output.json] [-s strip-prefix] [file]...

so you hand it some files, you optionally hand it an output file and a prefix to strip, and it does its thing. periodt. 💅

---

✨ DESCRIPTION ✨

okay so here's the tea 🍓: dwarf2sources lists out the source files that were used to create a given binary, and it gives you the whole thing in JSON format. very demure, very parseable.

but bestie, listen — the input files must not be stripped, and they must contain debugging information in DWARF format. if they're stripped? it's giving nothing. it's giving empty. don't do that to yourself. 😭

here's the flag menu, and every single one is a baddie in its own right:

• -h, --help — prints help information. when in doubt, ask for help, that's main character energy fr fr 🫶
• -V, --version — prints version information. know your version, love your version. ⭐
• -o, --output <output> — the file to write the JSON output to. your receipts, your JSON, your moment. 💾
• -s, --strip-prefix <strip-prefix> — strips the given prefix from comp_dir paths. lowkey the tidiest little glow-up for your paths. 🧚

---

👑 AUTHORS 👑

this program was written by Sjoerd Simons, based on the gimli 0.16.1 dwarfdump.rs example by Nick Fitzgerald, Philip Craig and other rust-dwarf developers. we love a collaborative slay. 🎀

---

🔥 SEE ALSO 🔥

• objdump(1)
• strip(1)

iykyk. go look at them if you want the extended universe. 🌈

---

and that's the whole vibe check on dwarf2sources(1) — straight from the section 1 manual, no cap, every flag accounted for, and not a single detail left on read. 💜 mwah. 💅