all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dann@ics.uci.edu, richardeng@foxmail.com, emacs-devel@gnu.org
Subject: Re: problem report #97: base/src/emacs/src/term.c (init_tty):RESOURCE_LEAK
Date: Mon, 08 Dec 2008 14:36:14 -0500	[thread overview]
Message-ID: <jwvk5aawjda.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1L9jAN-0006HK-8u@fencepost.gnu.org> (Eli Zaretskii's message of "Mon, 08 Dec 2008 11:41:03 -0500")

>> >     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




  reply	other threads:[~2008-12-08 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 15:56 problem report #97 Dan Nicolaescu
2008-12-08  7:07 ` problem report #97: base/src/emacs/src/term.c (init_tty): RESOURCE_LEAK Dan Nicolaescu
2008-12-08 14:05   ` Chong Yidong
2008-12-08 14:49     ` Chong Yidong
2008-12-08  9:11 ` Re: problem report #97: base/src/emacs/src/term.c (init_tty):RESOURCE_LEAK richardeng
2008-12-08 15:31   ` Dan Nicolaescu
2008-12-08 16:00   ` Stefan Monnier
2008-12-08 16:41     ` Eli Zaretskii
2008-12-08 19:36       ` Stefan Monnier [this message]
2008-12-08 23:28         ` Eli Zaretskii
2008-12-09  3:33           ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk5aawjda.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dann@ics.uci.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=richardeng@foxmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.