Comment 5 for bug 1095034

Hm, ok. To make a long story short, I saw llvm 3.2 was released recently and decided to take the latest trunk for a run in their static code analysis tool to see if it found anything new. And indeed it found a lot more issues than the previous run I had did.

Based on the dead assignments/divide by zero issues and what I remembered from last time, that part of the results seemed free of false positives. I have to admit though, that c++ is not the language I'm most proficient in, so a lot of these were more or less forwarded for others to take a look at. The thought about false positives did occur to me when I saw dereferenced null pointers had increased from one or two to more than 70 though, which is one of the reasons why I didn't do anything with them.

I apologize if these reports got rather noisy, as the goal was to identify issues in the code which can be discovered by using the right tools. The next time I see a sharp increase in some type of error, I'll post one or two instead to see whether it is considered a real issue or not. Again, I'm sorry and I hope I didn't ruin the new year for you already. :)