From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6082 invoked by alias); 20 Jun 2005 19:53:12 -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 6053 invoked by uid 22791); 20 Jun 2005 19:52:52 -0000 Received: from colo.khms.westfalen.de (HELO colo.khms.westfalen.de) (213.239.196.208) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 20 Jun 2005 19:52:52 +0000 Received: from khms.vpn ([10.172.192.2]:52699 helo=khms.westfalen.de) by colo.khms.westfalen.de with esmtpsa (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1DkSKA-0005AJ-B7 for gcc@gcc.gnu.org; Mon, 20 Jun 2005 21:52:50 +0200 Received: from root (helo=khms.westfalen.de) by khms.westfalen.de with local-bsmtp (Exim 4.50) id 1DkSK6-0004Kr-TD for gcc@gcc.gnu.org; Mon, 20 Jun 2005 21:52:46 +0200 Received: by khms.westfalen.de (CrossPoint v3.12d.kh15 R/C435); 20 Jun 2005 21:34:55 +0200 Date: Mon, 20 Jun 2005 19:53:00 -0000 From: kaih@khms.westfalen.de (Kai Henningsen) To: gcc@gcc.gnu.org Message-ID: <9ZF2rToXw-B@khms.westfalen.de> In-Reply-To: <200506192258.00250@gj-laptop> Subject: Re: c/c++ validator MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii References: <200506190024.18033@gj-laptop> <42B4D584.5080800@nycap.rr.com> <200506192258.00250@gj-laptop> X-No-Junk-Mail: I do not want to get *any* junk mail. X-Fix-Your-Modem: +++ATS2=255&WO1 X-SW-Source: 2005-06/txt/msg00923.txt.bz2 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.) MfG Kai