Jeffrey J. Early wrote:
- The crash does *not* occur when the application (either release or debug build) is launched within Xcode. - The crash *does* occur if I launch the app with gdb from the command line (same stack trace).
Inspect and then change things about your executable's runtime environment when Xcode launches it. The most common culprits are working directory or environment variables.
You can also try the opposite approach: run from the command-line with exactly the same runtime environment. The 'env' command can clear or set env-vars.
Another trick to help find differences: intentionally trigger a SEGV signal when running from Xcode. Compare the full list of libs loaded against the full list of libs from the unintentionally crashing app. Check the full pathnames of every dylib loaded.
Since the crash is apparently in dyld, maybe the cause is a DYLD_* env-var. There are also some helpful DYLD_* debugging env-vars you can try. See 'man dyld'.
-- GG _______________________________________________ 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
