Re: Various XCode 2.4.1 bugs (before I go ahead and file them)
Re: Various XCode 2.4.1 bugs (before I go ahead and file them)
- Subject: Re: Various XCode 2.4.1 bugs (before I go ahead and file them)
- From: Chris Hanson <email@hidden>
- Date: Fri, 17 Nov 2006 01:32:01 -0800
On Nov 17, 2006, at 12:36 AM, Florent Pillet wrote:
- Indexer crashes with incomplete code: while writing code and using
structs that are in the process of being defined, I often get "cc1
crashes" when saving or switching windows. It seems that the indexer
is not very resilient to compilation errors.
Given your mention of cc1, itsounds like a compiler stage is crashing
during predictive compilation. The indexer runs within Xcode; if it
were crashing, it would be Xcode that would crash.
Any cases where the compiler crashes -- whether during predictive
compilation or during a build -- should definitely be filed as a bug.
If at all possible, include the (preprocessed) code that causes the
compiler to crash.
Before taking the time to file bug reports, I wanted to check with
others about known bugs in XCode 2.4.1:
[snip]
For those which are not known yet, I'll file bugs in Radar.
My standard line on the topic: If you run into a bug, please file a
bug report regardless of whether it has been filed before, and don't
wait to find out if someone else has filed it. Bugs don't go into a
black hole -- even ones marked as duplicate!
Beyond the obvious use for prioritization, duplicate bug reports can
also wind up providing better reproduction cases, more useful stack
traces, useful system-configuration information, or a better "big
picture" when several reports are taken in aggregate. All of this can
be a big help towards the forehead-smacking "Oh, *that's* what's going
on!" moment that precedes a fix.
Just about the only time you shouldn't file a duplicate is when you're
told that something is an extremely well-known issue and that no more
duplicates are necessary. But if there's even a remote doubt about
whether something is known, file a bug.
-- Chris
_______________________________________________
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