Re: Upon break, debugger not showing correct line in source
Re: Upon break, debugger not showing correct line in source
- Subject: Re: Upon break, debugger not showing correct line in source
- From: Julian Gómez <email@hidden>
- Date: Mon, 15 Feb 2010 13:00:18 -0800
A couple of people have pointed out that bugreporter.apple.com bugs are not searchable because of the potential exposure of IP. The refers to both the bug report as well as bugs in Xcode.
Speaking from my development position: I ran into an Xcode bug that significantly slowed me down for more than a few days. It turned out that this was a known bug, but bugreporter would not let me know that. I could have been going faster sooner if that knowledge was accessible. As it was, I had to waste time repeating the discovery, and it took an effort by someone on the debugger team to figure it out, after which I filed a bug, only to be told it was a duplicate.
As for the IP issue: that of course is important. What if bugreporter worked differently? When filing a bug, it could ask you if the bug report can be public. If it can't, it could ask you to paste in some text describing the bug without posting anything confidential. Overall, it would be an opt-in process, but the motivator is to let others know that someone has found a problem. This would save a lot of developers needless duplicated effort and slowdown at finding the same problem all over again. The fact that openradar exists is justification for the need, but we all know that it's inherently not as comprehensive.
Again, what good is a knowledgebase if you can't access it.
--
Dr. Julian "a tribble took it" Gomez ** http://www.polished-pixels.com
_______________________________________________
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