Re: Finding where an app stalls
Re: Finding where an app stalls
- Subject: Re: Finding where an app stalls
- From: "Herb Petschauer" <email@hidden>
- Date: Tue, 12 Feb 2008 16:29:11 -0800
<http://developer.apple.com/technotes/tn2004/tn2124.html>
I'd start off by running sample (man sample) [also available via
Activity Monitor]. Actually, I'd probably start off with Shark
[Run menu, Start with Performance Tool, Shark]. When Shark launches,
select the Shark manual from the Help menu and read the Time Profiling
section.
You could also step through the code in the gdb debugger and see if
anything obvious jumps out (like a sleep(30) statement, not that I've
ever seen that - it was sleep(300)).
Good luck,
-H.
On 12/02/2008, Jeremy <email@hidden> wrote:
> Hey,
>
> After spending today figuring out why the Application won't build, I
> can't figure why it is stalling. Is there in easy way other than
> adding NSLog() to every other line to WHERE my application is stalling?
>
> Jeremy
> "How would a car function if it were designed like a computer?
> Occasionally, executing a maneuver would cause your car to stop and
> fail and you would have to re-install the engine, and the airbag
> system would say, 'Are you sure?' before going off." - Katie Hafner
>
>
> _______________________________________________
>
> 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
>
_______________________________________________
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