On 13 Jun '08, at 4:22 PM, Rod Schmidt wrote:
later on I get an EXC_BAD_ACCESS. Here's the stack trace where it usually happens (sometimes its different):#0 0x911546e8 in objc_msgSend #1 0x9331aed9 in _NSValuesAreEqual
A crash in objc_msgSend almost always means something's tried to message an already-dealloced object. In other words, you have a ref- counting error in your code, and too many -release messages got sent to the object in question, causing it to be dealloced even though the table still had a reference to it.
For discussion and debugging tips, see Q&A 1367 "Finding EXC_BAD_ACCESS bugs in a Cocoa project". (Which is an odd title; I've never had trouble _finding_ them, it's _fixing_ them that's hard.)
file:///Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/qa/qa2004/qa1367.html —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
