• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Static Analyzer doesn't always analyze all touched files?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Static Analyzer doesn't always analyze all touched files?


  • Subject: Re: Static Analyzer doesn't always analyze all touched files?
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 21 Jan 2014 07:39:13 -0800


On Jan 21, 2014, at 12:25 AM, Jerry Krinock <email@hidden> wrote:

After playing with this for about an hour I think that the reporting or non-reporting of memory management errors (at least) can only occur on the first Analyze after Build Settings have been touched, but may not. 

That doesn't match my experience — for me it's always been as you said you thought it worked: it analyzes all source files that have been touched since the last time Analyze was run.

Maybe there is something messed-up with your project, although I can't imagine what. It's odd that Clean didn't help; have you tried deleting the entire build directory?

—Jens

 _______________________________________________
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

References: 
 >Static Analyzer doesn't always analyze all touched files? (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Static Analyzer doesn't always analyze all touched files?
  • Next by Date: Re: Static Analyzer doesn't always analyze all touched files?
  • Previous by thread: Static Analyzer doesn't always analyze all touched files?
  • Next by thread: Re: Static Analyzer doesn't always analyze all touched files?
  • Index(es):
    • Date
    • Thread