Programs
A Mac program, library or object file opens as a page of what its headers say — the architectures it is built for, the systems it runs on, what it links to — and what macOS says of its signature. Use it to see whether a program runs natively, who signed it, or why it will not load a library.
What the keys do
| Key | Does |
|---|---|
| Enter | The menu of what can be done with it — nothing runs on one key unless you set the kind to Run |
| F3 | Shows this page |
| F4 | Nothing |
| ⇧F3 | Shows its bytes. There, F4 shows the text inside it instead |
What each key does can be changed — see Opening files.
Recognized by
- The name:
.dylib,.bundle,.oand.so. - What it starts with, for a file whose name says nothing — which is most programs, since they have no extension: a Mac program, whether for one architecture or several.
A program for Linux or Windows — by what it starts with, or named .exe or .dll — is recognized as
a program: Enter offers the menu, nothing runs. It is not read: F3 shows its bytes. So does a
.so built for Linux.
At a glance
| Key | Action |
|---|---|
| F2 | Next architecture |
| ⇧F2 | Previous architecture |
| ⇧F9 | All it says about itself |
| ⌥→ | Next file |
Architectures
A universal program holds a build for each architecture it runs on. They are listed at the top with their sizes, and the one this Mac runs is marked ► and shown below.
F2 shows the next and ⇧F2 the one before, round the ends. A program built for one architecture has no list and no key.
For the architecture shown:
- Type
- executable, dynamic library, bundle, object file, kernel extension and so on.
- Minimum OS, SDK
- The oldest system it runs on and the SDK it was built with, for each platform — a library can be built for macOS and Mac Catalyst at once.
- UUID, Entry point
- Its build’s identifier, and where it starts running.
- Install name
- For a library, the name programs link to it by, with its versions.
Its signature
The signature is checked by macOS, not read by the application, and arrives a moment after the rest — checking… until then, the architecture shown first.
- Signed
- yes, no, ad hoc — signed with no identity — or ad hoc, by the linker, as the build tools sign what they make.
- Valid
- yes, or no and the reason macOS gives.
- Identity, Issued by
- Who signed it, and the certificates that vouch for them.
- Team, Identifier
- The developer’s team and the identifier it was signed as.
- Hardened
- Whether it asks for the hardened runtime.
- Signed at
- When — by a time server where one was used.
- Entitlements
- How many it has. They are listed in full in the panel.
The check is of the program itself: an app’s other files around it are not checked. An object file has nothing for macOS to check, and says not signed.
What it is made of
- Segments
- Each segment’s size in memory and on disk, and its address.
- Linked libraries
- Each library with the versions it needs — marked weak, re-exported, lazy or upward where it is not simply required.
- Run paths
- Where it looks for a library whose name starts
@rpath/. - Unknown
- Load commands this page does not know, by number rather than left out.
The page scrolls with the arrows, the page keys, Home, End and the wheel.
A damaged file shows what could be read, then under Could not be read what could not — a file cut short still lists the architectures before the cut. A file with nothing in it that reads as a Mac program opens as bytes instead.
Everything in it
⇧F9 lists every architecture with its size and where it starts in the file, then all of
the one shown: the page above, whether it is 64-bit, and each entitlement as a key and its value —
com.apple.security.network.client, true.
The line underneath has the short form: the architectures, the type, and the signature in a few words — signed by …, ad hoc signed, not signed, signature invalid.
Going on to the next one
⌥→ or Space shows the next file in the pane’s order, and ⌥←, ⇧Space or ⌫ the one before — see going on to the next file.
Limits
- Headers and signature only: no disassembly and no symbols.
- An app is a folder, not a program: F3 does nothing on one. Its program is inside it, in
Contents/MacOS.