Hi,

It seems intermittent and I’m not sure if it is a bug or whether it has 
something to do with either some other project setting or to do with using some 
third party frameworks. I don’t really have much time at the moment to be able 
to investigate it further, but I’ll take another look when I have some time.

Has anyone else seen anything like this? 

Cheers
Dave

> On 17 Mar 2015, at 04:35, Joar Wingfors <[email protected]> wrote:
> 
> Hi Dave,
> 
> Please file a bug report. If you can attach a sample project, all the better. 
> 
> Thanks,
> 
> Joar
> 
> 
>> On 16 mar 2015, at 07:30, Dave <[email protected]> wrote:
>> 
>> Hi All,
>> 
>> I’m using XCode 6.2 - updated last Friday. I have my build settings set as 
>> follows:
>> 
>> Analyse During 'Build'                       YES
>> Mode of Analysis for ‘Analyse’       Deep
>> Mode of Analysis for ‘Build’                 Deep
>> 
>> Dead Stores                                  YES
>> Improper Memory Management   YES
>> Misuse of Grand Central Dispatch     YES
>> 
>> Before I updated, this worked fine, now, after updating it fails to run the 
>> Analyzer, or at least it doesn’t report problems even when there *is* a 
>> problem.
>> 
>> I’ve tried doing a Clean, a Clean Build Folder before building but it this 
>> has no effect.
>> 
>> Is there something else I need to do in order to make it work again?
>> 
>> Thanks a lot
>> Dave
>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Xcode-users mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/xcode-users/joar%40joar.com
>> 
>> This email sent to [email protected]
> 


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to