• 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
Solved Re: Debugging a crash in dyld
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Solved Re: Debugging a crash in dyld


  • Subject: Solved Re: Debugging a crash in dyld
  • From: Fritz Anderson <email@hidden>
  • Date: Fri, 24 Apr 2009 10:46:53 -0500

I figured it out.

I had gdb generate a log, and from there found my bad-access address (why didn't the gdb console tell me this?). atos told me it was NXArgc, _in my binary_. I discovered that #importing <Foundation/ NSDebug.h>, which is in the Simulator SDK, or declaring NSZombieEnabled extern, causes an access to NXArgc, crashing me at load.

My mistake was in trying to access NSZombieEnabled as a global variable. Setting it in the executable's environment variables got me zombies, with no crash.

I'll file a bug against NSDebug.h in the iPhone Simulator SDK.

	— F

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Debugging a crash in dyld (From: Fritz Anderson <email@hidden>)
 >Re: Debugging a crash in dyld (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: signal 11 (SIGSEGV) error
  • Next by Date: Re: Where to deploy byteswap.h?
  • Previous by thread: Re: Debugging a crash in dyld
  • Next by thread: Can't change the Active SDK back to iphone 2.0 stuck on 3.0
  • Index(es):
    • Date
    • Thread