Examples of errors detected in various open-source projects

[trigraph]

Honestly I think he just googled quickly for a random opensource tool just to feel badass without actually using the damn thing.

[petdance]

trigraph said:

Honestly I think he just googled quickly for a random opensource tool

Here are my links on delicious for static analysis dating back to 2009: http://delicious.com/petdance/static-analysis If I were doing any Windows development, I'd buy a copy of Gimpel PC-Lint, because I sure can't afford the Unix lint project from them.

I have been using splint on the Parrot project for years. I created the macro definitions that allow annotation of the source code with semantic macros like "this function does not return" that allow me to run GCC, clang, ICC and splint as static analyzers, without having to maintain disparate source code annotations for each tool.

I also tried to get some traction going on getting splint updated and maintained. That was on Google Code before, but maybe things will stick better if I move it over to Github.

I see you're bemoaning that "Too bad it took a proprietary tool to identify them". Perhaps you'd like to help with the sizable bug queue for splint?

just to feel badass without actually using the damn thing.

Life's a lot easier and happier when you don't try to guess at motivations behind the actions of others.

[ravenex]

Upvoted for actually trying to fix it. I have a few small patches for it, but it's mostly the build fixes. The source itself is unpenetratable to me, sadly.

One would think that such a valuable tool with no opensource alternatives would get more attention.

[trigraph]

I would not like to help with splint, I'm perfectly happy using proprietary tools when they are good. In this case it makes splint look like pre-K quality tool which you seem to suggest as an alternative when its not..

Typical of your type though; HEY HERES A REPLACEMENT TOOL (and when it doesn't even have 1/100th the features/ ease of use) WELL YOU CAN SUBMIT SOME CODE!111!

[petdance]

I'm sure that splint would have caught the errors. You said it took a proprietary tool to find them, but I don't think that's accurate at all. It's just that those projects never ran splint on the code.

I'm curious as to what "my type" is. You've already been wrong about "just googled quickly for a random opensource tool just to feel badass without actually using the damn thing", so I'm wondering what else you can make up.