On Wed, Sep 3, 2008 at 9:23 PM, RGA <[EMAIL PROTECTED]> wrote: > Putting aside for now whether this is the right way to implement, my > question is how are messages processed? What is the maximum stack depth for > number of recursive messages? How is this affected by the introduction of > 64bit frameworks? Is there a way to see the current stack depth > auto-magically? What happens in the event of the message handling stack > becoming full and is there a way to deal with this event? >
Some of these questions are answered in QA1419: <http://developer.apple.com/qa/qa2005/qa1419.html> Although you may think of the stack in terms of stack-frames, what really matters to the operating system is the memory footprint of the stack (since each frame isn't a constant size---it varies depending on the memory requirements of the called method). You can examine the current stack (in terms of frames---more specifically, return addresses) using backtrace(3): <http://developer.apple.com/documentation/Darwin/Reference/ManPages/man3/backtrace.3.html> Generally though, if you're hitting the stack size limit, you're doing something wrong. Phil _______________________________________________ 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 [EMAIL PROTECTED]
