From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8508 invoked by alias); 20 Jun 2005 20:58:03 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 8473 invoked by uid 22791); 20 Jun 2005 20:57:53 -0000 Received: from s0106000d3a2b2987.vc.shawcable.net (HELO thinkpaddie.zlew.org) (24.86.96.131) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 20 Jun 2005 20:57:53 +0000 Received: from thinkpaddie (thinkpaddie [127.0.0.1]) by thinkpaddie.zlew.org (Postfix) with ESMTP id F288833B262 for ; Mon, 20 Jun 2005 22:57:26 +0200 (CEST) From: Tommy Vercetti To: gcc@gcc.gnu.org Subject: Re: c/c++ validator Date: Mon, 20 Jun 2005 20:58:00 -0000 User-Agent: KMail/1.8.50 References: <200506190024.18033@gj-laptop> <200506192258.00250@gj-laptop> <9ZF2rToXw-B@khms.westfalen.de> In-Reply-To: <9ZF2rToXw-B@khms.westfalen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506202257.24965@gj-laptop> X-SW-Source: 2005-06/txt/msg00925.txt.bz2 On Monday 20 June 2005 10:12, Kai Henningsen wrote: > vercetti@zlew.org (Tommy Vercetti) wrote on 19.06.05 in <200506192258.00250@gj-laptop>: > > I was looking on different ones, for C, that claimed to have ability to > > find security problems. One that I found the best, is splint. But it's > > still not able to find such obvious problem: > > Did you look at sparse? That seems to do quite a useful job on the Linux > kernel (which is, of course, the main reason for its existence). I don't > really have an idea how good it would be on non-kernel C code. (Not C++, > obviously.) sparse is fairly primitive. So far splint does the job, almost. And only for C :/ -- Vercetti