PC-lint from Gimpel has set the standard for static code analysis: it is used by many companies developing safety critical applications. Additionally PC-lint can check the MISRA rules which are standard for many coding guide lines. PC-lint has detected many subtle bugs in my sources. Thank you, PC-lint!
CodeWarrior classic provided a plugin for the PC-lint compiler: To bad that this does not exist in the eclipse based CodeWarrior. You might think that given PC-lint so popular, there should be an eclipse plugin available? Yes, there are many attempts on this: all of them did not work well enough for me. The good news: There is the Linticator eclipse plugin. The bad news: it is not for free.
The Linticator plugin has been developed at the IFS (Institute for Software) in Rapperswil/Switzerland. You can register at the linticator.com web site and you get a 30 day evaluation license.
Linticator nicely integrates into eclipse, and adds a new IDE menu:
Using a wizard, I can configure the different settings:
Enabling Linticator for a project is just a context menu away:
The plugin integrates into eclipse CDT as a builder:
Running Linticator on a project reports the PC-lint messages to the Problems View:
The source files show the proper markers. Ignoring a message is simple: Linticator comes with a plugin named ‘QuickFixes’. I can use the context menu to ignore a message:
This automatically inserts the comment to tell PC-lint to ignore that message:
To get an explanation on a message, I use the ‘Show Documentation’ context menu:
The Linticator plugin costs CHF 500 (~US$550). Yeah, that’s high compared to the US$390 for PC-lint itself. That’s a total of US$850 per user. On the other side: Linticator integrates PC-lint very nicely into eclipse. Or what is the price of one bug in my software?
Unfortunately, my 30 day evaluation license run out of time. Too bad! While trying to get the funds in my department to buy Linticator, I’ll explore other ways how to use PC-lint with eclipse.