Re: Xcode debugger quality
Re: Xcode debugger quality
- Subject: Re: Xcode debugger quality
- From: Jerry <email@hidden>
- Date: Thu, 1 May 2008 11:19:43 +0100
On Wed, Apr 30, 2008 at 10:11 PM, Jim Crafton < email@hidden> wrote: > Am I alone in my frustration with the debugger? Are others out there also
> experiencing the same issues?
Definitely not. I long ago reverted to using printf for nearly all my debugging. The debugger only stops at breakpoints when it feels like it. If by some miracle it does stop at one, you have to wait for ages before the dreaded "timed out fetching variables" message. If you do see any variables, they often say "Out of scope". Data formatters pretty well never work - you have use "View as memory" to see the contents of practically any non-primitive type. e.g. Those "First", "Last" and "All" buttons for STL types - what are they for? I've never seen them show anything. It gets confused by any sort on inlined code, and it's a total lottery whether pressing Step In will step in, over or just continue. Breakpoints often don't go away when you delete them, so you have to quit the debugger just because you've got a persistent breakpoint in a loop. Startup time is terrible - it takes two or three minutes for the debugger to start up on my Quad core Mac Pro. In that time I can add several printfs, compile and run.
On the other hand, just to show that I'm not just a whiner, Shark is a totally awesome tool and I won't hear anything said against it. There's nothing better in existence.
Jerry
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden