From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5686 invoked by alias); 18 Aug 2007 01:05:44 -0000 Received: (qmail 5473 invoked by uid 22791); 18 Aug 2007 01:05:42 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 18 Aug 2007 01:05:39 +0000 Received: from kahikatea.snap.net.nz (62.40.255.123.static.snap.net.nz [123.255.40.62]) by viper.snap.net.nz (Postfix) with ESMTP id 697EE3DA961; Sat, 18 Aug 2007 13:05:36 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 034368FC6D; Sat, 18 Aug 2007 13:05:33 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18118.17885.89039.298330@kahikatea.snap.net.nz> Date: Sat, 18 Aug 2007 01:05:00 -0000 To: msnyder@sonic.net Cc: gdb-patches@sourceware.org Subject: Re: NEWS for 6.7: mention coverity bug fixes In-Reply-To: <10983.12.7.175.2.1187377963.squirrel@webmail.sonic.net> References: <10983.12.7.175.2.1187377963.squirrel@webmail.sonic.net> X-Mailer: VM 7.19 under Emacs 22.1.50.10 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-08/txt/msg00352.txt.bz2 > *** Changes since GDB 6.6 > > + * 58 Coverity issues resolved in gdb, 29 in bfd, 1 in libiberty, and > + 1 in opcodes. These include such things as resource leaks, null pointer > + dereference, use after free, and array overruns. > + > * When looking up multiply-defined global symbols, GDB will now prefer the > symbol definition in the current shared library if it was built using the > -Bsymbolic linker option. I can imagine that Coverity would like recognition when their software is successfully used to find bugs in free software projects, but I don't think that NEWS is the right place to do it. This file details what changes have been made to GDB, not how they were made or how many were made. You already mention Coverity in the ChangeLogs, which seems the right thing to do. _They_ can then use this as evidence to any claims that they might wish to make about their software. -- Nick http://www.inet.net.nz/~nickrob