Re: EXC_BAD_ACCESS mystery
Re: EXC_BAD_ACCESS mystery
- Subject: Re: EXC_BAD_ACCESS mystery
- From: Nava Carmon <email@hidden>
- Date: Wed, 11 Nov 2009 20:20:09 +0200
Thanks a lot for the tip...
BTW, it's a RubyCocoa application. The case with zombie object was
hard to understand where does it come from...
since the object, that was reported was a ABMultiValueCoreDataWrapper
object, that was retained after it was released, but the stack showed
something else.
I wonder if the following usage of valueAtIndex can be the reason for
it:
str = pProp.valueAtIndex(i).to_s?
or trying to get a label of multivalue in case of only one value in
property?
like
pProp = pp.valueForProperty(OSX::KABPhoneProperty)
if pProp != nil && pProp.count > 0
pProp.count.times { |i|
phone = {}
phone[:Name] = pProp.labelAtIndex(i).to_s.match(/^_\$!<(.*)>!\$_$/)[1]
phone[:Number] = pProp.valueAtIndex(i).to_s
contact[:M] << phone
}
Sorry for posting here a ruby code, but just in case, may be you can
help with it?
There is no RubyCocoa list on apple, although RubyCocoa is a part of
OS X. Official RubyCocoa forum almost is not alive...
Thanks again,
Nava
On Nov 11, 2009, at 6:05 PM, Corbin Dunn wrote:
On Nov 10, 2009, at 8:56 PM, Nava Carmon wrote:
Thank you Corbin for your great post.
How do I track the following issue with instruments:
*** attempt to pop an unknown autorelease pool
ObjectAllocator with NSZombieEnabled doesn't react on this. I could
track the same case you explained in your post, but it doesn't work
for pool autorelease.
How to handle it?
Break on CFLog and look at the backtrace (NOTE: CFLog is a private
method, and should not be called, but breaking on it is okay).
corbin
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden