Re: Xcode debugger quality
Re: Xcode debugger quality
- Subject: Re: Xcode debugger quality
- From: "Bill Lowrey" <email@hidden>
- Date: Thu, 1 May 2008 10:57:36 -0500
FWIW, The debugger was the reason my company moved to CodeWarrior from Xcode 1.1. We've obviously had to come back, and the positive thing is that the debugger is IMO much better than it used to be. It usually works now, at least for me, and at least so far. It doesn't work as well as it should, but I'm fairly tolerant given how bad it was.
I've never used gdb from the command-line. Is it any more reliable when used directly? Would it be worth trying?
Even when the Xcode interface to the debugger couldn't display a variable, gdb always had the right data. If you are having consistent problems with variable display timeouts, make friends with the gdb prompt. It's better than NSLog and/or printf. Is it a pain? Yeah. Is it better than having nothing? Yep.
The whole GUI debugging experience seems to work much better with DWARF than with stabs, so if anyone hasn't moved to DWARF yet, I'd recommend it.
Just my .02.
Bill Lowrey
Sr. Software Engineer
istation.comOn Thu, May 1, 2008 at 10:31 AM, James Larcombe <
email@hidden> wrote:
> Roy Lovejoy wrote:
>
> > IIRC, Metrowerks Codewarrior used gdb for OSX, and
> > although a smidge slower than its OS 9 versions, still
> > performed high quality debugging, without any of Xcode's
> > issues.
>
> That's not my recollection; the quality of the Codewarrior
> debugger reduced dramatically when it moved to GDB, in
> terms of both speed and reliability.
>
> James
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (
email@hidden)
> This email sent to
email@hidden>
_______________________________________________
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