Sonny Bonds on Nostr: Any dyld/linkage experts out there that can make a wild guess as to why one plugin ...

Any dyld/linkage experts out there that can make a wild guess as to why one plugin (ours) in loaded in a host process would call straight into another (someone else's)? On macOS.

I think our plugin is calling std::generic_category() but ends up in another module instead of libc++. (Can't reproduce it locally so my context is limited.)

Address in target module is always the same relative its base, which makes me think it's somewhat deliberate and not a jump to garbage address.

#cpp