[Adium-devl] Apparently clang's static analyzer can handle Adium

[Ryan Govostes]

I've just run the analyzer on r24417. I also wrote a Python script  
that takes two tables and combines them with the following heuristic  
for matching reports:

1. They're the same report type (memory leak, etc.)
2. They're in the same file
3. They're < 20 lines apart

I merge changes into the new table after pairing up reports; I also  
link to the previous report and give a line offset.

Next, I take the remaining false positive reports and stick them in an  
appendix table. If this isn't useful to anyone, I can take it out.

What I'm confused about is why a handful of "fixed" problems are still  
showing up in the reports table; either a) my script is confused, b)  
the fixes weren't actually fixes, or c) they've become false positives.


While I look forward to a much smarter algorithm for remembering  
reports across builds, this allows me to update the table with  
significantly less work.

And, congrats on reducing the report count from 314 to 150 since  
r24211 :-)

Regards,
Ryan Govostes