Re: debugger wonkiness
Re: debugger wonkiness
- Subject: Re: debugger wonkiness
- From: Don Quixote de la Mancha <email@hidden>
- Date: Fri, 04 May 2012 12:52:12 -0700
On May 3, 2012, at 9:02 PM, John Michael Zorko <email@hidden> wrote:
>
> Don,I'm with you -- my first computer was an 1802-based RCA COSMAC VIP, and I had to learn 1802 machine code before I could get it to do anything. Debugging was difficult back then, but that was 1981. I learned C on an Atari ST and got used to printf-style debugging, but that was 1987. Assertions and OOP methodologies aside, it's now 2012, and while it's good that I can still use the old techniques when needed, it's concerning that Xcode4's debugging environment demands their continued usage because simple things like step-into and step-over (among other things) are less than reliable.
>
John,
Does GDB work if you use it's command-line interface in the Terminal?
If it does, while not as harmonious as the GUI it would be a lot more productive than just using printf.
Whether or not it does work, reporting what happens when you try would be helpful to Apple's tools people when you file your bug.
I've had this same thing happen as I've mentioned, and you report that your coworkers see it as well.
There must be so many coders using Xcode at Apple itself that if Xcode's developers spread the word through the company's internal channels that they needed to see it with their own eyes, some other Apple employee surely would find a reproducible case for them.
For purely internal Apple consumption, the tools engineers could write a special build of Xcode that had logging and was loaded with assertions.
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com/
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