• 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: Crash on Intel machine
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash on Intel machine


  • Subject: Re: Crash on Intel machine
  • From: James Bucanek <email@hidden>
  • Date: Thu, 1 Mar 2007 07:55:20 -0700

Kish wrote on Thursday, March 1, 2007:
>Thread 6 Crashed:
>0   libobjc.A.dylib                    0x90a54387 objc_msgSend + 23
>1   com.apple.AppKit                   0x934101ad +[NSApplication
>_startDrawingThread:] + 120
>2   com.apple.Foundation               0x925f536c forkThreadForFunction
>+ 123
>3   libSystem.B.dylib                  0x90023d87 _pthread_body + 84

Anytime an application crashes with an EXC_BAD_ACCESS in objc_msgSend, I immediatlely suspect that a message is being sent to a deallocated object. Set some NSZombie <http://developer.apple.com/technotes/tn2004/tn2124.html> variables and run your app again.

--
James Bucanek
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: 
 >Re: Crash on Intel machine (From: Kish <email@hidden>)

  • Prev by Date: appleEvent?
  • Next by Date: Re: Array exception when changing the bounds size of a view
  • Previous by thread: Re: Crash on Intel machine
  • Next by thread: invalid CIContext with CGLContext initialization method?
  • Index(es):
    • Date
    • Thread