I have some code that is throwing EXC_BAD_ACCESS. It does so when an object is 
deallocating, in its -dealloc method on a call to [super dealloc]. The object's 
class's superclass is NSObject. Here's the (relevant part of the) stack trace:

#0      0x7fff872e016d in _class_hasCxxStructorsNoSuper
#1      0x7fff872e0741 in object_cxxDestructFromClass
#2      0x7fff872e60f8 in objc_destructInstance
#3      0x7fff872e06f5 in _internal_object_dispose
#4      0x7fff83e0279a in -[NSObject(NSObject) dealloc]
#5      0x10007b18e in -[ZPOauthParams dealloc] at ZPOauthParams.m:57

I know I must have blown something, but I have no idea what I could have done 
to cause this sort of problem. If anyone has seen something like this before, 
please let me in what direction I should look for the problem. TIA.

_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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 arch...@mail-archive.com

Reply via email to