On Jan 12, 2009, at 4:58 PM, Brandon Walkin wrote:
I'm the developer of BWToolkit. Some users have run into this problem where the framework would work fine for them for a while, and then one day it would output the warnings that Joseph mentioned. My Xcode/gcc knowledge is a bit lacking, so I haven't been able to figure this one out. Do you know what changes have to be made in the BWToolkit Xcode project to fix this issue?
Just to clarify... this looks like a warning from GDB, so it should not affect anything in a released application. You should only see the warning if you choose "Build > Build and Debug" or "Build > Build and Go", not "Build > Build and Run".
I've noticed I get this warning in my app, too, for my embedded Sparkle framework. I've never much paid attention to it, since I don't plan on debugging Sparkle. Plus, I figured it was just gdb complaining about not being able to find symbols in a stripped binary.
Upon further investigation, the error "(file not found)" seems to imply that it can't find the file, which is clearly not the correct error message. Furthermore, I took a quick glance at the gdb sources [1], and noticed that it only resolves @executable_path. I'm guessing gdb needs to be updated to properly support @loader_path and @rpath. Namely the dyld_library_basename() looks incorrect. I'm gonna file a bug about this.
-Dave [1]: http://www.opensource.apple.com/darwinsource/DevToolsOct2008/gdb-962/src/gdb/macosx/macosx-nat-dyld-path.c _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
