NSMutableString *theString = [[NSMutableString alloc] init];

for (int i=0; i<100; i++)
{
[theString appendFormat:@"%d ",i] ;
}

NSLog(@"theString is: %@", theString);

Not really sure why. I never release theString. This is caught easily by the Instruments Leaks tool, but CLANG doesn't catch it.

char b[15];

char a[50]=”aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa”;
strcpy(b,a);

Surprisingly the xcode unable to detect simple buffer overflow issue. I tried with GCC 4.2, LLVM GCC 4.2 and clang LLVM 1.0. No issue detected. Is these any bench mark available for xcode analysis. How much effective is this?

Thanks for the tip! I suspected that Clean had that effect, but I’m glad to hear it confirmed. Unfortunately, after running Clean I no longer get any static analysis results in the Build Results window when I think I should (ex: synthesized properties not released in dealloc). I made sure that “Run Static Analyzer” is enabled in the Project Settings, and this seems to happen regardless of which compiler version I’m using. I’m not sure how I could have broken it, but you never know. Thoughts? I hope I can get this working; the more insight I have into my code, the better.

Cheers.

Anyone else have any insight on Clang LVM ??

John

Thanks for the article. Clang appears to be a great tool and I would love to add it to my kit, but I’ve run into a few problems:

When I try to set the C/C++ Compiler Version in my Project Settings to Clang LLVM 1.0, I get the error “Library not found for -lgcc” when I attempt to build in Xcode. When I use the system default compiler (GCC 4.2), I can get static analysis to work on a per-file basis when I Build & Analyze. I would like to rebuild and analyze all files with Clang, but I’m guessing that I need to Touch each file to have Xcode include it in the build process.

Are there benefits to using Clang LLVM 1.0 as the compiler, or is using GCC and leaving “Run Static Analyzer” checked in the Project Settings enough? Any advice would be appreciated.

Thanks, and keep up the great work.

-(unsigned long long) computeEntryValue
{
NSUInteger length= [self.entryString length];
NSUInteger digit;
NSUInteger i;
// declared and initialized here
unsigned long long evalue=0;
for(i=0;i= ’0′ && c = ‘A’ && c <= 'F')
digit = 10+c-'A';
evalue = evalue * base + digit;
}
return evalue;
}

The analyzer says that evalue is undefined. However, digit is uninitialized this should have been detected.

I posted a question on the iPhone Dev Tips Google Group to see if anyone knows the how to set the default compiler to LLVM-Clang:

http://groups.google.com/group/iPhoneDeveloperTips/t/e4cb6b9a642049a8