RE: Xcode 3.1.2 ( downloaded from iPhone SDK 9m2621afinal )Debugger bugged : Won't stop at break points ?
RE: Xcode 3.1.2 ( downloaded from iPhone SDK 9m2621afinal )Debugger bugged : Won't stop at break points ?
- Subject: RE: Xcode 3.1.2 ( downloaded from iPhone SDK 9m2621afinal )Debugger bugged : Won't stop at break points ?
- From: A Gift for You <email@hidden>
- Date: Tue, 14 Apr 2009 17:37:05 -0700
I saw this thread a few weeks ago when I had an unrelated problem with
Xcode 3.1.2. Sadly, I now have the problem addressed in this thread
-- breakpoints specified in Xcode for my iPhone application are
ignored when the application is executed in the debugger.
I was somewhat annoyed when I saw Chris Espinosa's response to this
thread at the time -- and was a bit more annoyed when I encountered it
again. Chris was obviously angered for some reason by a poster trying
to clue the Apple development community in on their valid perceptions
of the current build of Xcode. There were other posts in a similar
vein which did nothing to answer the original question either, but
simply attacked people reporting instability.
It is a complete waste of my scarce and valuable development time to
have to wade through these senseless attacks like the one made by
Chris Espinosa while trying to find a solution to a very serious
misconfiguration, design flaw, or bug in Xcode. It may help if such
trolls re-read (or read for the first time) Apple's tips for mailing
list netiquette: http://lists.apple.com/tips.html Please don't
bother posting if you can't help solve the problem.
We are already sold on Apple and know that there are people are
getting paid to work on XCode. We would very much like to see
debugging working in XCode without having to re-install our operating
system as poor unguided Trinh decided to do.
I strongly encourage Chris to redirect his defensive stance against
Apple developers to an offensive stance against Xcode instability --
if Chris had expent the same amount of energy communicating with the
Xcode team about developer perception of XCode 3.1.2 rather than
haranguing a dissatisfied customer/developer, our development
community would be better off. Further, it would have been a much
better use of Chris Espinosa's time if he could have offered a modicum
of advice to the original poster regarding the very honest and very
specific problem he was facing rather than defending what many
perceive to be least stable Xcode they have encountered in years.
Christopher
_______________________________________________
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