A VM Address. It's not specific to cache dylibs vs input dylibs

A VMOffset can be in the cache or an input dylib. It's mostly going to be used to translate from one to the other

A VM Size within a cache dylib. Eg, the size of a segment

A file size within a cache dylib. Eg, the file size of a segment

A VM Address inside the shared cache

A VM Address inside a dylib which is a cache input

Note, this should match PLATFORM_* values in <mach-o/loader.h>

a type-safe va_list wrapper

A file offset within an input dylib. Eg, the file size of a segment

A file size within an input dylib. Eg, the file size of a segment

Used by accelerator tables in dyld shared cache

for detecting symlinks and hard links, so dyld does not load same file twice

MARK: --- ProtectedStackReturnType --- The work() lambda called by the with*() functions may be called from a read-write stack, but ultimately return

A file offset within a cache dylib. Eg, the file size of a segment

A VM Size within a cache input dylib. Eg, the size of a segment

The base class for patch tables. Forwards to one of the subclasses, depending on the version Note that the version 1 table doesn't use the struct bel

This iterator is a series of nodes and indexes used to sequentially walk an ordered tree. An iterator with 0 depth is the end iterator. As an internal

Represents the holes left by the selector placement algorithm, to be filled later with other selectors we did not target.

A VM offset inside a dylib which is a cache input

The difference between 2 VM addresses might be a size, or might be an offset This handles both, allowing for implicit conversions to the one we need

Filter to find individual symbol re-exports in trie

The difference between 2 VM addresses might be a size, or might be an offset This handles both, allowing for implicit conversions to the one we need