Re: How to debug crash on startup of 64-bit build
Re: How to debug crash on startup of 64-bit build
- Subject: Re: How to debug crash on startup of 64-bit build
- From: Greg Guerin <email@hidden>
- Date: Tue, 6 Jul 2010 11:51:27 -0700
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 (email@hidden)
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:
This email sent to email@hidden