site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com I am using CFBundleLoadExecutableAndReturnError to load a plug-in. When the plug-in fails to load, the errors returned from CFBundle seem to be…not helpful. For example, when it fails to load due to linking issues, I can't seem to find anything in the error report that tells me the symbol that couldn't be found. All I have is the error code (always 3588) and a rudimentary string "The bundle Foo.bundle could not be loaded." Since CoreFoundation calls dlerror internally, I can't call it when CFBundleLoadExecutableAndReturnError fails, and I don't see any other functions I can call to retrieve this info from CFBundle/CFError. (CFErrorCopyDescription, etc. seem to return the same canned strings.) Is there some other way of determining the actual dyld errors that occured without using dlopen()? I can't switch to using dlopen(), as that seems to mess up CFBundle in other ways, but it's a real drag having to call dlopen() whenever CFBundleLoad... fails just so I can retrieve the error information. I tried using the deprecated functions in <mach-o/dyld.h> but those don't return anything useful either. Thanks, Ryan ----------------------- Ryan _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com