Comments on: Cocoa Tutorial: How to Crash Cocoa http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/ Taglines are for Windows programmers Mon, 26 Jul 2010 16:50:30 +0000 hourly 1 http://wordpress.org/?v=3.0 By: sdfisher http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/comment-page-1/#comment-44 sdfisher Sun, 09 Mar 2008 21:45:18 +0000 http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/#comment-44 <p>I'm just starting Cocoa development, and I imagine you've already saved me a bunch of time. :)</p> I’m just starting Cocoa development, and I imagine you’ve already saved me a bunch of time. :)

]]> By: erik http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/comment-page-1/#comment-43 erik Sun, 09 Mar 2008 16:32:29 +0000 http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/#comment-43 <p>Any time you have a SIGSEGV you have a memory problem. They generally come in three forms: 1) You accesses freed/deallocaed memory 2) You used an un-initialized pointer 3) You have a buffer over-run memory corruption</p> <p>The first thing to do in a Cocoa application is turn on NSZombieEnabled. http://www.cocoadev.com/index.pl?NSZombieEnabled "with zombies enabled, messages to deallocated objects will no longer behave strangely or crash in difficult-to-understand ways, but will instead log a message die in a predictable and debugger-breakpointable way."</p> Any time you have a SIGSEGV you have a memory problem. They generally come in three forms: 1) You accesses freed/deallocaed memory 2) You used an un-initialized pointer 3) You have a buffer over-run memory corruption

The first thing to do in a Cocoa application is turn on NSZombieEnabled. http://www.cocoadev.com/index.pl?NSZombieEnabled “with zombies enabled, messages to deallocated objects will no longer behave strangely or crash in difficult-to-understand ways, but will instead log a message die in a predictable and debugger-breakpointable way.”

]]> By: Marcus Zarra http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/comment-page-1/#comment-42 Marcus Zarra Sat, 08 Mar 2008 17:07:46 +0000 http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/#comment-42 <p>Paul,</p> <p>Yes there are plenty of ways to get around this issue in that direction. However, it involves code which I was trying to avoid.</p> Paul,

Yes there are plenty of ways to get around this issue in that direction. However, it involves code which I was trying to avoid.

]]> By: PixelSmack http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/comment-page-1/#comment-41 PixelSmack Sat, 08 Mar 2008 10:48:47 +0000 http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/#comment-41 <p>I had this problem, fortunately it was in a very small app and i quickly figured out where the problem was. I didn't think the stack was much use though!</p> I had this problem, fortunately it was in a very small app and i quickly figured out where the problem was. I didn’t think the stack was much use though!

]]> By: Paul http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/comment-page-1/#comment-40 Paul Sat, 08 Mar 2008 10:37:10 +0000 http://www.cimgf.com/2008/03/08/cocoa-tutorial-how-to-crash-cocoa/#comment-40 <p>So, is there a way to have it release when closed, but allocate a new instance when needed?</p> So, is there a way to have it release when closed, but allocate a new instance when needed?

]]>