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
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
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 autorele
On Nov 10, 2009, at 5:37 AM, Ian Piper wrote:
> Hi all,
>
> Can anyone advise a good strategy for tracking down EXC_BAD_ACCESS crashes? I
> have an application that I can run quite happily two out of three times. Then
> it will crash with this error. By this I mean I can do Build and Run
> su
To Jens and Ryan,
Thanks for the pointers - very helpful.
Ian.
--
___
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.
These might also be helpful:
http://www.cocoadev.com/index.pl?DebuggingTechniques (in particular see the
"Breaking on Exceptions" section where they talk about objc_exception_throw)
http://chanson.livejournal.com/171198.html
Then, when you crash, bring up the Debugger (Cmd-Shift-Y). Sometimes you
On Nov 10, 2009, at 5:37 AM, Ian Piper wrote:
Can anyone advise a good strategy for tracking down EXC_BAD_ACCESS
crashes? I have an application that I can run quite happily two out
of three times. Then it will crash with this error. By this I mean I
can do Build and Run successively with n
NSZombieEnabled should help track down your memory error.
http://www.cocoadev.com/index.pl?NSZombieEnabled
On Tue, Nov 10, 2009 at 8:37 AM, Ian Piper wrote:
> Hi all,
>
> Can anyone advise a good strategy for tracking down EXC_BAD_ACCESS crashes?
> I have an application that I can run quite happ
Hi all,
Can anyone advise a good strategy for tracking down EXC_BAD_ACCESS
crashes? I have an application that I can run quite happily two out of
three times. Then it will crash with this error. By this I mean I can
do Build and Run successively with no problems and then it will crash
- n
