LLVM-OTOOL(1)

💅 LLVM-OTOOL — the Mach-O dumping tool (yes, that's the manual name, it's llvm-otool, from LLVM, bestie)

🌸 SYNOPSIS

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

✨ DESCRIPTION

Okay so llvm-otool is a tool for dumping Mach-O files. That's the whole vibe. 💖

The tea here is that it attempts to be command-line-compatible and output-compatible with macOS's otool. Like, it's trying to match its whole energy. 🫶

---

🎀 OPTIONS 🎀

Let's go through literally every single one, no skipping, I promise:

• -arch <value> — picks out the slice of a universal Mach-O file. Choose your fighter. 🦋
• -C — prints linker optimization hints.
• -D — prints the shared library id.
• -d — prints the data section.
• -f — prints universal headers.
• -G — prints the data-in-code table.
• --help-hidden — prints help for the hidden flags 👀 (iykyk).
• --help — prints help. The regular kind.
• -h — prints the mach header.
• -I — prints the indirect symbol table.
• -j — prints opcode bytes.
• -L — prints the used shared libraries.
• -l — prints load commands. (Lowercase, bestie — do not confuse it with -L 😭)
• -mcpu=<value> — selects the cpu for disassembly. Note the = — it's giving -mcpu=<value>, not a space. 💀
• -o — prints the Objective-C segment.
• -P — prints the __TEXT,__info_plist section as strings.
• -p <function name> — starts disassembly at <function name>.
• -r — prints relocation entries.
• -s <segname> <sectname> — prints the contents of a section. Two args, both required, in that order. 🎯
• -t — prints the text section.
• --version — prints the version.
• -V — symbolizes disassembled operands (and it implies -v, so you get verbose for free ✨).
• -v — verbose output / disassemble when printing text sections. Two moods, one flag.
• -X — omits leading addresses or headers.
• -x — prints all text sections. yes, all of them. 👑
• @<FILE> — reads command-line options and commands from the response file <FILE>. Iconic little at-sign moment. 🍓

---

🔥 EXIT STATUS

llvm-otool exits with a non-zero exit code if there's an error. Otherwise? It exits with code 0. Slay. ✅

💀 BUGS

Wanna report a bug? Please visit [the link below] — literally this one:

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

(The original line breaks it as https://github.com/llvm/llvm-project/labels/tools:llvm-objdump/ — same URL, just wrapped in the manpage. 🫶)

🌈 SEE ALSO

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

👑 AUTHOR

Maintained by the LLVM Team (https://llvm.org/). Shoutout to the whole team, fr fr. 💜

🧚 COPYRIGHT

2003-2023, LLVM Project

---

ngl that's the whole page, bestie — every flag, every path, every number, untouched. Main character energy only. 💅

okay bye, this was LLVM-OTOOL(1), page 15, dated 2023-01-14 — mwah 💖 see u in the group chat ✨