From: Jari Aalto <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: [ITA] splint 3.1.1 - Check C programs for security vulnerabilities
Date: Tue, 14 Aug 2007 15:36:00 -0000 [thread overview]
Message-ID: <lkce163w.fsf@blue.sea.net> (raw)
Adopted from Elfyn McBratney
Jari
sdesc: "Check C programs for security vulnerabilities and programming
mistakes."
ldesc: "Splint does many of the traditional lint checks including
unused declarations, type inconsistencies, use before definition,
unreachable code, ignored return values, execution paths with no
return, likely infinite loops, and fall through cases. More powerful
checks are made possible by additional information given in source
code annotations. Annotations are stylized comments that document
assumptions about functions, variables, parameters and types. In
addition to the checks specifically enabled by annotations, many of
the traditional lint checks are improved by exploiting this additional
information."
category: Devel
requires: cygwin
a) manual
wget \
http://cygwin.cante.net/splint/splint-3.1.1-2.tar.bz2 \
http://cygwin.cante.net/splint/splint-3.1.1-2-src.tar.bz2 \
http://cygwin.cante.net/splint/setup.hint
b) automated: get.sh displays further instructions
gpg --keyserver wwwkeys.pgp.net --recv-keys 955A92D8
mkdir splint ; cd splint
rm -f get.sh get.sh.sig
wget http://cygwin.cante.net/splint/get.sh \
http://cygwin.cante.net/splint/get.sh.sig
gpg --verify get.sh.sig get.sh &&
sh get.sh
next reply other threads:[~2007-08-14 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 15:36 Jari Aalto [this message]
2007-08-14 15:54 ` Mark Harig
2007-08-15 15:55 ` Dr. Volker Zell
2007-08-24 22:05 ` Jari Aalto
2007-08-26 10:08 ` [GTG] " Dr. Volker Zell
2007-08-27 12:26 ` Eric Blake
2007-08-26 14:53 ` idirectscm
2007-08-26 15:40 ` Jari Aalto
2007-08-27 8:31 ` Dr. Volker Zell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lkce163w.fsf@blue.sea.net \
--to=jari.aalto@cante.net \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).