PC-lint for C/C++ was first introduced in
1985. It will thoroughly check your C/C++ source code for bugs, glitches,
inconsistencies, non-portable constructs, and much more, so you can find
and fix your bugs more quickly, and more economically,
than with traditional debugging procedures
PC-lint for C/C++ runs on Microsoft Windows
FlexeLint for C/C++
The demand for PC-lint checking for non-Windows development led to the
introduction of FlexeLint in 1988. FlexeLint is distributed as
shrouded C source code, to make the capabilities of PC-lint available
wherever there is a C compiler to compile it.
FlexeLint for C/C++ runs on all systems that support
a C compiler, including all variants of UNIX.
Version 9.00 Patches
The current patch level is
This patch provides many bug fixes and enhanced checking for MISRA.
See our bug fix file
Upcoming Product with Modern C++ support
With the ever evolving C++ language specifications, it is no secret that the last few
years have proven particularly challenging for us. In order to continue to provide
outstanding static analysis while at the same time ensuring that adopters of the most recent
C++ standards are well-served, we have decided to make a major change in our product line
which you can read about
As the year comes to a close, we at Gimpel Software would like to thank our faithful users
for their support during the past 30 years. We are honored to have so many thousands of programmers
using PC-lint and FlexeLint to write better code. Our users are among the most astute and talented
programmers in the world and they have provided us with invaluable feedback and suggestions which
have enabled our developers to make PC-lint and FlexeLint into the most comprehensive static
analyzers for C/C++ available anywhere. We are excited about the future of PC-lint and look
forward to continued service to the C and C++ communities.
Our Response to GrammaTech's allegations |
A so-called "whitepaper" produced by Grammatech and comparing CodeSonar
with PC-lint was recently brought to our attention by several of our users.
We felt compelled to set the record straight and correct
the many errors found in that paper.
Celebrating 30 Years of PC-lint
PC-lint started 30 years ago as a stop-gap measure for a simple operating system with
limited memory to solve a problem (matching function arguments to their parameters) that no
longer exists. Over the course of time, it has evolved to become a highly flexible system of
finding deep bugs and security breaches and is now arguably the most widely used, fully-featured,
C/C++ static analyzer on the planet.
Software That Checks Software: The Impact of PC-lint |
"James Gimpel gives some fascinating insights into the growth, technology, and
impact of the very widely used static analyzer,
PC-lint in the never-ending battle against the bug."
IEEE Software, vol. 31, no. 1, pp. 15-19, Jan.-Feb. 2014
Interactive Demo now supports multi-module checking |
Although PC-lint has been providing multi-module checking since version 1.0 was
released in May of 1985, our on-line demo was set up to process only one source file at a time.
That has just changed. You can now enter several C, C++ and header files into the
online demo to see the power of inter-module checking that PC-lint and FlexeLint have had
from the beginning.
Just follow the set up directives at
Introducing Multiple Modules (MM).
A Bug a Month? It's Harder Than You Think |
Have you ever wondered who's been writing our "Bug of the Month" ads for the past 18 years?
Among all those ads, which one has been the most controversial?
To find out, read an interview of the "legendary Jim Gimpel" by Dr. Dobb's Journal editor,
Interactive Demo |
Did you ever encounter a snippet of C or C++ code that you wanted to
quickly test against Gimpel lint? Check out our new
Interactive Demo. We provide several source files for you
to lint and modify. There's
even a blank slate for your own creations.
Just type or copy your code into the code box, click "Analyse"
and see what happens.
Lint is still a champ at detecting errors
For this review, I prepared a small C file with obvious bugs in
it and asked each vendor to run it at the most
sensitive bug-sniffing levels. Coverity, due to its
detection philosophy, found zero; Klocwork found five.
PC-lint generated 15 warnings. Here, however, is the critical
difference. Only PC-lint correctly identified a miscoded function
call. All vendors agreed this call could generate a null-pointer
exception, which is a showstopper in C and C++ and a specific target
of the reviewed suites.
Andrew Binstock, InfoWorld, January 30, 2006
Each year one product is inducted into the Front Line Awards Hall of Fame.
The inductee is chosen for its outstanding contribution to the game
development industry. This year's honor was presented to Gimpel Software's
PC-lint. PC-lint is a tool for programmers which enables them to search
for thousands of types of common errors in their game's C and C++ source code.
Even after a decade of availability, PC-lint continues to be the tool of
choice to verify cross-platform compatibility and source code validity with
the highest standards
Game Developer Magazine Press Release, Dec. 11, 2000,
See page 13 in the archives.
Home | Contact
PC-lint and FlexeLint are trademarks of Gimpel Software LLC
Copyright © 2016, Gimpel Software LLC, All rights reserved.