From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: problem report #97: base/src/emacs/src/term.c (init_tty):RESOURCE_LEAK Date: Mon, 08 Dec 2008 11:41:03 -0500 Message-ID: References: <200812011556.mB1Fu6jE015153@mothra.ics.uci.edu> <200812081711503879659@foxmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1228755277 12189 80.91.229.12 (8 Dec 2008 16:54:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Dec 2008 16:54:37 +0000 (UTC) Cc: dann@ics.uci.edu, richardeng@foxmail.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 08 17:55:40 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 1L9jOS-0008C2-1M for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2008 17:55:36 +0100 Original-Received: from localhost ([127.0.0.1]:41694 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9jNH-00061w-4W for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2008 11:54:23 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L9jB5-0002L8-FO for emacs-devel@gnu.org; Mon, 08 Dec 2008 11:41:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L9jB1-0002JB-Ku for emacs-devel@gnu.org; Mon, 08 Dec 2008 11:41:45 -0500 Original-Received: from [199.232.76.173] (port=52871 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L9jB0-0002Ip-Pu for emacs-devel@gnu.org; Mon, 08 Dec 2008 11:41:42 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:56171) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L9jB0-0000cO-DZ for emacs-devel@gnu.org; Mon, 08 Dec 2008 11:41:42 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1L9jAN-0006HK-8u; Mon, 08 Dec 2008 11:41:03 -0500 In-reply-to: (message from Stefan Monnier on Mon, 08 Dec 2008 11:00:30 -0500) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:106683 Archived-At: > From: Stefan Monnier > Date: Mon, 08 Dec 2008 11:00:30 -0500 > Cc: Dan Nicolaescu , emacs-devel > > > 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?