LLVM-OTOOL(1)

📦
version 14.0.6 · 8 versions
, in ubuntu questing

✨ LLVM-OTOOL(1) ✨

okay bestie, welcome to the llvm-otool page, straight outta the LLVM manual set 💖 this one's a little tool with main character energy, so let's get into it.

🎀 NAME 🎀

llvm-otool — a Mach-O dumping tool. that's it, that's the job, and it does it flawlessly. 💅

🦋 SYNOPSIS 🦋

llvm-otool [option…] [file…]

🌸 DESCRIPTION 🌸

so like, llvm-otool is a tool for dumping Mach-O files. that's the whole vibe. 🫶

and here's the slay: it attempts to be command-line-compatible and output-compatible with macOS's otool. so if you already know otool, you already know her. no cap. 💯

💜 OPTIONS 💜

  • -arch <value> — pick which slice you want out of a universal Mach-O file. choose your fighter ✨
  • -C — print linker optimization hints. lil notes the linker left behind 📝
  • -D — print the shared library id.
  • -d — print the data section.
  • -f — print universal headers.
  • -G — print the data-in-code table.
  • --help-hidden — print help for the hidden flags 👀 the secret menu, iykyk
  • --help — print help.
  • -h — print the mach header.
  • -I — print the indirect symbol table.
  • -j — print opcode bytes.
  • -L — print used shared libraries.
  • -l — print load commands.
  • -mcpu=<value> — select the cpu for disassembly. lowercase l, bestie, don't come for me 🔥
  • -o — print the Objective-C segment.
  • -P — print the __TEXT,__info_plist section as strings.
  • -p <function name> — start disassembly at <function name>. jump right in 🏊
  • -r — print relocation entries.
  • -s <segname> <sectname> — print contents of a section. two args, both required, no skipping 🎯
  • -t — print the text section.
  • --version — print version.
  • -V — symbolize disassembled operands (and yes, this implies -v, so it's a two-for-one 💖).
  • -v — verbose output / disassemble when printing text sections.
  • -X — omit leading addresses or headers. minimalism era 🌿
  • -x — print all text sections.
  • @<FILE> — read command-line options and commands from the response file <FILE>. it's like a little snack pack of args 🍓

💀 EXIT STATUS 💀

llvm-otool exits with a non-zero exit code if there's an error. otherwise? it exits with code 0. clean. iconic. no notes. 👑

🙈 BUGS 🙈

to report bugs, please visit:

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

(the original wraps that URL across a line with a hyphen-thing, but it's one link, bestie, go click it 🫶)

🌈 SEE ALSO 🌈

llvm-nm(1), llvm-objdump(1)

👑 AUTHOR 👑

Maintained by the LLVM Team (https://llvm.org/). they're the parents of this whole ecosystem fr fr 💜

2003-2025, LLVM Project

and that's the page!! ✨ 14 whole pages of manual glory, dated 2025-05-22, brought to you by LLVM-OTOOL(1) herself. mwah. go dump some Mach-O files, you got this 💅💖🌈

📦 where this page comes from