Printable View
Hi all,
I am working on a project to create a MISRA C code checker to verify if the code/program is compliant to the MISRA C 2004 rules.
Can someone let me know what are the similar code checkers/tools that are currently available in the market ?
Also, where could I get the source code of these code checkers?
I have no idea on how these code checkers are being developed, so I would like to have a sample of source code of the checker.
Hope to hear from you guys soon.
Thanks!
PC-lint/FlexeLint MISRA 1998 C Checking
I only know about this one, but it isn't free (it is very good though).
Thanks for your info.
Do you know where could I get the sample source code of such a tool?
Splint Home Page
In the style of lint, but not really like it at all in detail (and not MISRA C either).
But you do get source code.
Thanks Salem! That really helps!
Does anyone know what are the differences between Klocwork and Misra-C Code checker?since both are also static code checkers.
What are the errors or warnings do not covered by Klocwork but Misra-C tool or vice versa?
Which tool is better?
Well, they both fail to discover non-trivial bugs that can only be foun dusing a combination of two other tools -
LOL....you are right!!
but anyway, I am still looking for some opinions and information for the doubts I have in my previous reply. I need these information for my presentation on this Friday.
Could someone please help?
Thank you!!
actually I am looking for some strong points to convince my company management to approve my project (creating a MISRA-C code checker).
Currently, we have been using Klocwork as a static code checker in our workplace, so I guess the management would probably question me about the differences between Klocwork and Misra-C checker as well as the benefits/strength of MISRA-C checker over Klocwork.
Without the strong points to convince them, I guess they would not approve my project.
Greatly appreciated if someone could help.
Someone explained MISRA C as a great way for managers to be able to verify the validity of code, not just the syntax.
By flicking a switch, if the compiler is setup to check for MISRA C, it will generate those errors.
The issue comes down to the need to use a compiler setup for MISRA C. Not only that, but you are bound by a 3rd party's interpretation of these rules, which may be too strict or not strict enough for your company. This starts to get really complicated if different compilers are used in your company. Example someone is compiling under VisualDSP++ (embedded systems compiler) and somone else is compiling under MULTI (Green Hills Integrity compiler, Integrity has been DO-178B certified). Which compiler is giving you the best results?
A stand alone tool gives you the ability to bring developed code to an even playing ground. A home grown tool gives you the added flexibility that this tool is tailored to your specifications.
Hope this helps your cause.
Scott