LLVM-OTOOL(1)

💅 LLVM-OTOOL(1) — the Mach-O dumping tool, bestie edition

okay so welcome to llvm-otool(1) from the LLVM fam — this is the manual page, and I'm gonna walk you through it like we're texting at 2am 🦋

---

✨ NAME ✨

llvm-otool — Mach-O dumping tool. that's it, that's the whole vibe. it dumps Mach-O files. 👑

---

🌸 SYNOPSIS 🌸

llvm-otool [option...] [file...]

options first, files after, everyone gets along. simple. 💜

---

🎀 DESCRIPTION 🎀

so llvm-otool is a tool for dumping Mach-O files. literally its whole personality, and honestly? it ate.

it attempts to be command-line-compatible and output-compatible with macOS's otool. so like, if you already know otool, you already know this. no cap. 🫶

---

🔥 OPTIONS 🔥

okay this is the long section, stay with me babe, every single one is here:

• -arch <value> — picks which slice of a universal Mach-O file you want. universal file = many slices, you pick one. ✨
• -chained_fixups — prints chained fixup information.
• -C — prints linker optimization hints. cute little hints.
• -dyld_info — prints bind and rebase information.
• -D — prints the shared library id.
• -d — prints the data section.
• -f — prints the universal headers.
• -G — prints the data-in-code table.
• --help-hidden — prints help for the hidden flags 👀 the secret menu.
• --help — prints help. the normal menu.
• -h — prints the mach header.
• -I — prints the indirect symbol table.
• -j — prints opcode bytes. raw bytes, no thoughts, head empty 💀
• -L — prints the used shared libraries.
• -l — prints load commands. that's a lowercase L btw, not a one. lowercase L is the busy one here. 🙈
• -mcpu=<value> — selects the cpu for disassembly.
• -o — prints the Objective-C segment.
• -P — prints the __TEXT,__info_plist section as strings.
• -p <function name> — starts disassembly at <function name>. so you can jump straight to your fave function, main character energy fr fr.
• -r — prints relocation entries.
• -s <segname> <sectname> — prints the contents of a section. two arguments, not one — don't get caught lacking on that.
• -t — prints the text section.
• --version — prints the version.
• -V — symbolizes disassembled operands, and yes it implies -v. you get verbose whether you asked or not, bestie. 😭
• -v — verbose output, and also disassembles when printing text sections.
• -X — omits leading addresses or headers. the ✨minimalist✨ option.
• -x — prints all text sections. all of them. every last one.
• @<FILE> — reads command-line options and commands from the response file <FILE>. like a playlist but for flags 🎧

---

⭐ EXIT STATUS ⭐

llvm-otool exits with a non-zero exit code if there's an error. otherwise it exits with code 0. so like, zero = she's fine, not-zero = something's up. vibe check passed or failed, no in-between. 💅

---

💀 BUGS 💀

found a bug? don't suffer in silence, bestie — go report it here:

https://github.com/llvm/llvm-project/labels/tools:llvm-objdump/

(that link got a lil line-broken in the original, but it's one URL, i promise 🫶)

---

🌈 SEE ALSO 🌈

• llvm-nm(1)
• llvm-objdump(1)

go read those too, they're literally cousins of this one. iykyk. 🧚

---

👑 AUTHOR 👑

maintained by the LLVM Team (https://llvm.org/). iconic behavior honestly.

---

💖 COPYRIGHT 💖

2003-2025, LLVM Project

---

and that's the whole page, bestie — every flag, every path, every section, nothing skipped. you're basically an otool expert now. 🍓

kisses, and remember: this was page 19 of the LLVM manual set, dated 2025-01-17, from the LLVM source — see you in the next manpage, mwah 💋🌸