From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: Re: Memory leak Date: Sun, 25 May 2008 11:02:35 +1200 Message-ID: <18488.40587.106202.28276@kahikatea.snap.net.nz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1211670179 21197 80.91.229.12 (24 May 2008 23:02:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 24 May 2008 23:02:59 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 25 01:03:38 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K02m2-0006Tw-1H for ged-emacs-devel@m.gmane.org; Sun, 25 May 2008 01:03:38 +0200 Original-Received: from localhost ([127.0.0.1]:56155 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K02lH-0007KD-Bj for ged-emacs-devel@m.gmane.org; Sat, 24 May 2008 19:02:51 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K02lB-0007GK-4M for emacs-devel@gnu.org; Sat, 24 May 2008 19:02:45 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K02l9-0007Ck-AU for emacs-devel@gnu.org; Sat, 24 May 2008 19:02:44 -0400 Original-Received: from [199.232.76.173] (port=43455 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K02l9-0007Ca-6j for emacs-devel@gnu.org; Sat, 24 May 2008 19:02:43 -0400 Original-Received: from viper.snap.net.nz ([202.37.101.25]:43502) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K02l8-0002ZD-JL for emacs-devel@gnu.org; Sat, 24 May 2008 19:02:42 -0400 Original-Received: from kahikatea.snap.net.nz (47.31.255.123.static.snap.net.nz [123.255.31.47]) by viper.snap.net.nz (Postfix) with ESMTP id 0481D3DA613 for ; Sun, 25 May 2008 11:02:37 +1200 (NZST) Original-Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 62E2D8FC6D; Sun, 25 May 2008 11:02:36 +1200 (NZST) X-Mailer: VM 7.19 under Emacs 22.2.50.2 X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:97671 Archived-At: I'm joining the thread a bit late but anyway: Instead of Valgrind, which has been shown to be unsuitable several times, how about using Coverity to identify the source of the memory leak(s)? Ben Chelf the CTO for Coverity said "we have set up a framework internally to continually scan open source projects" and I have the impression that they scan the most recent Emacs source, or at least can. Is anyone still signed up to access their reports? If not, is it worth approaching them again? -- Nick http://www.inet.net.nz/~nickrob