From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: problem report #97: base/src/emacs/src/term.c (init_tty):RESOURCE_LEAK Date: Mon, 08 Dec 2008 14:36:14 -0500 Message-ID: References: <200812011556.mB1Fu6jE015153@mothra.ics.uci.edu> <200812081711503879659@foxmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1228765002 16957 80.91.229.12 (8 Dec 2008 19:36:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Dec 2008 19:36:42 +0000 (UTC) Cc: dann@ics.uci.edu, richardeng@foxmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 08 20:37:46 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 1L9lvE-0004X4-LR for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2008 20:37:36 +0100 Original-Received: from localhost ([127.0.0.1]:44958 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9lu3-0005Bw-Km for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2008 14:36:23 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L9lty-0005Ba-Nw for emacs-devel@gnu.org; Mon, 08 Dec 2008 14:36:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L9ltx-0005BG-DV for emacs-devel@gnu.org; Mon, 08 Dec 2008 14:36:18 -0500 Original-Received: from [199.232.76.173] (port=47592 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9ltx-0005BD-6U for emacs-devel@gnu.org; Mon, 08 Dec 2008 14:36:17 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:64686 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L9ltw-0004kx-5F; Mon, 08 Dec 2008 14:36:16 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEALQFPUlLd+Db/2dsb2JhbACBbM0jgwWBJg X-IronPort-AV: E=Sophos;i="4.33,736,1220241600"; d="scan'208";a="30796844" Original-Received: from 75-119-224-219.dsl.teksavvy.com (HELO pastel.home) ([75.119.224.219]) by ironport2-out.teksavvy.com with ESMTP; 08 Dec 2008 14:36:14 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 54B168219; Mon, 8 Dec 2008 14:36:14 -0500 (EST) In-Reply-To: (Eli Zaretskii's message of "Mon, 08 Dec 2008 11:41:03 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:106690 Archived-At: >> > What tool do you use to check the Emacs memory leak? I just know >> > valgrind doesn't work. >> >> IIRC someone mentioned getting valgrind to work (maybe without dumping >> and with some extra work?). If someone could add some blurb about it in >> etc/DEBUG that would be helpful. Even if it doesn't work fully, adding >> some info about what was tried can be useful for the next one who >> tries it. > etc/DEBUG already includes a section about running under "malloc > debuggers", doesn't that work with valgrind? It doesn't work for "grep"pers like myself. Stefan