Re: Static analyzer being lazy
Re: Static analyzer being lazy
- Subject: Re: Static analyzer being lazy
- From: Chris Espinosa <email@hidden>
- Date: Sun, 06 Sep 2009 11:25:52 -0700
On Sep 5, 2009, at 1:56 PM, Aron Nopanen <email@hidden> wrote:
Further investigation revealed that 'clang --analyze' was being
called, but reported no errors. I tried creating a new project, put
the same sorts of violations into a file in that project, and ran
analysis...that time I got the expected warnings.
Not sure what's so different about the first file...
Was the first file perhaps C++ or Objective-C++?
Chris
On 5/09/2009, at 7:19 PM, I wrote:
Keen to try out the new static analyzer integration in Xcode 3.2 on
Snow Leopard, I loaded a method with violations that would be sure to
raise its ire (including some copied directly from Apple's examples
for same), and hit 'build and analyze'. The build reported no issues.
I've tried doing a clean build, changing the compiler to clang and
doing a clean build, turning on the 'run static analyzer' build flag
in the project properties and doing a clean build, swearing at it and
doing a clean build...nothing. I looked in the console logs and saw
nothing.
Anybody else had this trouble? What to check next?
Cheers,
Aron
_______________________________________________
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
_______________________________________________
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