• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How to debug crash on startup of 64-bit build
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to debug crash on startup of 64-bit build


  • Subject: Re: How to debug crash on startup of 64-bit build
  • From: Ken Thomases <email@hidden>
  • Date: Tue, 6 Jul 2010 12:30:03 -0500

On Jul 6, 2010, at 11:47 AM, Jeffrey J. Early wrote:

> I just transitioned my (primarily Cocoa based) code from building 32-bit i386/PPC, to also include x86_64. Unfortunately, when launching the 64-bit version I'm getting a crash at launch and I can't figure out how to debug it. Stack trace at the bottom of the email.
>
> - 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).

> Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
>
> Application Specific Information:
> objc[9001]: garbage collection is ON
>
> Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
> 0   libobjc.A.dylib               	0x00007fff8300a715 _read_images + 1617
> 1   libobjc.A.dylib               	0x00007fff83020835 map_images_nolock + 1266
> 2   libobjc.A.dylib               	0x00007fff830099a0 map_images + 114
> 3   dyld                          	0x00007fff5fc0395f dyld::notifyBatchPartial(dyld_image_states, bool, char const* (*)(dyld_image_states, unsigned int, dyld_image_info const*)) + 763

...

That crash suggests to me that the binaries are corrupt.  Have you tried a full clean and rebuild?

The fact that it doesn't crash when launched from Xcode suggests that the Executable (in the project) has some environment variables set that aren't present in a "naked" launch.  Or possibly there's some support for strange build options.  For example, you don't have Zero Link or Fix and Continue enabled, do you?

Regards,
Ken

_______________________________________________

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

References: 
 >How to debug crash on startup of 64-bit build (From: "Jeffrey J. Early" <email@hidden>)

  • Prev by Date: Re: How to debug crash on startup of 64-bit build
  • Next by Date: NSTextField fieldeditor subclass example? (and an unrelated other inquiry)
  • Previous by thread: Re: How to debug crash on startup of 64-bit build
  • Next by thread: Re: How to debug crash on startup of 64-bit build
  • Index(es):
    • Date
    • Thread