• 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: Isolating a bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Isolating a bug?

  • Subject: Re: Isolating a bug?
  • From: "M. Uli Kusterer" <email@hidden>
  • Date: Wed, 6 Apr 2005 13:37:02 +0200
At 6:46 Uhr -0400 06.04.2005, Gregory Weston wrote:
From a program that's been shipping for about a year now without stability complaints, I user sent a crash log that I find vexing. Why? Because here's the call stack.

That bug looks suspiciously like you're stomping memory somewhere. Often this is when you're releasing an object that you don't own but access it later on. This will often work fine several times because the memory hasn't been reused and thus still contains the data from the previous (valid) object, and then suddenly part of it gets re-used and everything goes bang, either in your object, or in the object that got the re-used space assigned, because you changed it through a call to your released object.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
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: 
 >Isolating a bug? (From: Gregory Weston <email@hidden>)

  • Prev by Date: Re: Undo manager
  • Next by Date: Re: Isolating a bug?
  • Previous by thread: Isolating a bug?
  • Next by thread: Re: Isolating a bug?
  • Index(es):
    • Date
    • Thread