I've been using Gimpel's PC-Lint for a long time and really like it a
lot. It's a commercial product but it's pretty cheap for a single seat
license at $239: http://www.gimpel.com/. PC-Lint runs on Windows, but
their Flexelint product runs on *nix's.
Splint is open-source & free though and should be able to detect similar
problems I would think. I tried it once or twice but was already
comfortable with PC-Lint so I never made the switch:
http://www.splint.org/download.html.
Wikipedia & answers list more static analysis tools as well, quite a few
of which are open source:
http://www.answers.com/topic/list-of-tools-for-static-code-analysis
http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis
If you're thinking of using PC-Lint, I can post the options file and
scripts I'm using to give you a head start. I'm not really doing
anything fancy though, but it might possibly help to get started. I've
purposely not quieted lint too much for now, but I would think that many
of the warnings would want to be turned off so it's easier to focus on
the more problematic ones - at least initially. I'm also not using any
of the advanced features yet either such as function mimicry, value
tracking, etc. There are plenty of warnings to sift through already
without having lint generate even more.
- Chris
(By the way, full descriptions of lint warnings I submit using Gimpel's
tool can be read here: http://www.gimpel.com/html/pub80/msg.txt. It's
located on their "Lint 8.00 Patches" page.)
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-
> bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
> Sent: Thursday, August 21, 2008 3:30 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Lint of packet-tcp.c
>
>
> On Aug 13, 2008, at 8:00 AM, Maynard, Chris wrote:
>
> > Some time ago when Wireshark was still Ethereal, I had run lint
> > against
> > one or more of the dissectors and provided some results to the
mailing
> > list and offered to provide lint output for more dissectors if there
> > was
> > interest, but there didn't appear to be any at the time.
>
> When you say "lint", to what flavor of lint are you referring? We
> might want to include it in buildbot builds.
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-dev
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.