Re: Xcode debugger quality
Re: Xcode debugger quality
- Subject: Re: Xcode debugger quality
- From: Simon Wilson <email@hidden>
- Date: Thu, 1 May 2008 12:46:52 +0200
> the dreaded "timed out fetching variables" message
Are you still getting this on 3.0? I got this a lot with 2.4 but 3.0
has solved it for me.
> On the other hand, just to show that I'm not just a whiner, Shark
is a totally awesome tool
That goes for ObjectAllocations functionality in Instruments too,
which is simply fantastic. Microsoft's tools are appalling by
comparison: clunky, unsupported internal tools they're too embarrassed
to release to the general public (at least this was the case in 2006)
which we were only granted access to by virtue of a premium support
contract.
Why can't Apple get the debugger beyond first base? Is gdb simply that
bad? Is Apple not experiencing these problems in testing or with their
own development?
A reliable debugger is the bare-minimum foundation for a decent tool
chain, closely following the compiler. How does Apple debug their
applications like Logic, Final Cut, Aperture etc (assuming these apps
are developed with the publicly-accessible version of Xcode)?
I've never used gdb from the command-line. Is it any more reliable
when used directly? Would it be worth trying?
Simon
_______________________________________________
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