Open helje5 opened 3 years ago
Alternatively, you could dump the shared cache and save the link graph, as I expect this to only be a problem if an app links a system framework that transitively links AppKit.
Alternatively you can just launch the app, stop it, and see what's loaded into the process.
Alternatively, you could dump the shared cache and save the link graph
How would I do this?
You can use something like https://github.com/saagarjha/dyld-shared-cache-big-sur to grab all the files and they read the dependencies from everything.
macOS BS has the "dyld shared cache" which breaks running
objdump
on the dependencies. E.g. this results in BS Safari not having any features detected.W/ the "dyld shared cache", the
/System/Library/PrivateFrameworks/Safari.framework
doesn't actually exist on disk anymore (henceobjdump
can't analyse it).Maybe we can use
dlopen
to load and open an executable and then somehow traverse the link list (w/o actually executing the binary)?