• 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: Drawing crash - not near my code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Drawing crash - not near my code!


  • Subject: Re: Drawing crash - not near my code!
  • From: Uli Kusterer <email@hidden>
  • Date: Fri, 25 Nov 2005 18:56:49 +0100

Am 25.11.2005 um 17:00 schrieb Evan Olcott:
Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

It's a bad access error. You must've stomped on system memory somewhere. It's just crashing inside system functions because that's where the system accesses the memory you corrupted. That's why memory bugs are so hard to track down: You change some un-allocated (or already released) memory and it doesn't blow up in your face until someone else uses the memory you just overwrote.


I'm a little surprised that a head programmer didn't spot that one immediately...

Cheers,
-- M. Uli Kusterer
http://www.zathras.de


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Drawing crash - not near my code! (From: Evan Olcott <email@hidden>)

  • Prev by Date: Re: Suspected bug (was: Removing focus rings from NSImageViews)
  • Next by Date: Re: Is Apple's singleton sample code correct?
  • Previous by thread: Drawing crash - not near my code!
  • Next by thread: Is Apple's singleton sample code correct?
  • Index(es):
    • Date
    • Thread