LLVM-OTOOL(1)
π LLVM-OTOOL(1) β bestie's guide to the Mach-O dumping tool
okay so welcome to llvm-otool, a lil tool from the LLVM squad (that's the manual section 1 btw, for the girlies keeping track of their man page sections β¨). She dumps Mach-O files. That's her whole thing. And she's so good at it.
β¨ NAME β¨
llvm-otool β Mach-O dumping tool π¦
πΈ SYNOPSIS πΈ
llvm-otool [option...] [file...]
π DESCRIPTION π
So llvm-otool is a tool for dumping Mach-O files. That's it, that's the job. π
And here's the tea: she tries to be command-line-compatible and output-compatible with macOS's otool. Like, she's out here matching otool's energy on both the flags you type and the output you get back. Compatibility queen. π
π OPTIONS π
okay bestie, this is the long part, but every single one matters, no skipping:
-arch <value>β pick which slice of a universal Mach-O file you wanna look at.-chained_fixupsβ print the chained fixup info.-Cβ print linker optimization hints.-dyld_infoβ print bind and rebase info.-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 (yes, there are secret flags, iykyk π).--helpβ print help.-hβ print the mach header.-Iβ print the indirect symbol table.-jβ print opcode bytes.-Lβ print the shared libraries that are used.-lβ print load commands.-mcpu=<value>β pick the cpu for disassembly.-oβ print the Objective-C segment.-Pβ print the__TEXT,__info_plistsection as strings.-p <function name>β start disassembling at <function name>.-rβ print relocation entries.-s <segname> <sectname>β print the contents of a section (you give it the segment name and the section name, two args, no cap).-tβ print the text section.--versionβ print version.-Vβ symbolize the disassembled operands. (she implies-v, so it's a two-for-one situation π )-vβ verbose output / disassemble when printing text sections.-Xβ omit the leading addresses or headers.-xβ print all text sections.@<FILE>β read command-line options and commands from the response file <FILE>.
π EXIT STATUS π
llvm-otool bails out with a non-zero exit code if there's an error. No error? She exits with code 0. Clean. Immaculate. Periodt. β¨
π BUGS π
Found a bug? bestie please tell the devs, don't just suffer in silence π go here:
https://github.com/llvm/llvm-project/labels/tools:llvm-objdump/
π₯ SEE ALSO π₯
π AUTHOR π
Maintained by the LLVM Team (https://llvm.org/). They're doing the lord's work fr fr. π«Ά
π COPYRIGHT π
2003-2025, LLVM Project
and that's the whole page, bestie!! this was LLVM-OTOOL(1) from LLVM version 20, dated 2025-09-03 πΈ go dump some Mach-O files, you absolute icon, and remember: compatibility is the vibe πβ¨π
π¦ where this page comes from
- fedora 43: llvm20 20.1.8-2.fc43 Β· Apache-2.0 WITH LLVM-exception OR NCSA
- fedora 43: llvm20 20.1.8-2.fc43 Β· Apache-2.0 WITH LLVM-exception OR NCSA
- fedora 44: llvm20 20.1.8-2.fc44 Β· Apache-2.0 WITH LLVM-exception OR NCSA
- fedora 44: llvm20 20.1.8-2.fc44 Β· Apache-2.0 WITH LLVM-exception OR NCSA
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms