Static code analysis (splint or pc-lint)

Go To Last Post
3 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,

Do any of you professionals use either splint, under Windoze, or PC-Lint to analyse your AVR source code for errors ?

I am new to C coding and it has been suggested to me that doing static analysis is a good idea as it could stop a lot of silly mistakes and save a lot of debugging time.

Would it be worth including this or some other code analysis tool in the WinAVR distribution ?

Would it be possible to integrate it as a tool into AVRStudio 4.13, so you could just hit a button on the toolbar to run the analyser ?

Your comments please.

Thanks
Howard

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

gcc itself does quite a good job, if you compile with -Wall.

Leon

Leon Heller G1HSM

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

To integrate it into Studio I think you'd need to get the Studio plugin SDK

As for which is "best". We use Gimpel's pc-lint professionally but it's fairly expensive and during a recent review of procedures one of our staff did a comparison of splint and pc-lint and was fairly impressed by the "cheaper" version.