all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: "richardeng" <richardeng@foxmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: problem report #97: base/src/emacs/src/term.c (init_tty):RESOURCE_LEAK
Date: Mon, 8 Dec 2008 07:31:25 -0800 (PST)	[thread overview]
Message-ID: <200812081531.mB8FVP59017353@mothra.ics.uci.edu> (raw)
In-Reply-To: <200812081711503879659@foxmail.com> (richardeng@foxmail.com's message of "Mon, 8 Dec 2008 17:11:51 +0800")

"richardeng" <richardeng@foxmail.com> writes:

  > Dan Nicolaescu <dann@ics.uci.edu> writes:
  > 
  >   > CID: 97
  >   > Checker: RESOURCE_LEAK (help)
  >   > File: base/src/emacs/src/term.c
  >   > Function: init_tty
  >   > Description: Returned without freeing storage "area"
  >   > 
  >   > Event alloc_fn: Called allocation function "xmalloc" [model]
  >   > Event var_assign: Assigned variable "area" to storage returned from "xmalloc"
  >   > Also see events: [var_assign][leaked_storage]
  > 
  > Hi, Dan
  >     What tool do you use to check the Emacs memory leak? I just know valgrind doesn't work.
  >     It seems the above report is generated by some tool.
  >     Thank you!

See http://permalink.gmane.org/gmane.emacs.devel/106398




  reply	other threads:[~2008-12-08 15:31 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 [this message]
2008-12-08 16:00   ` Stefan Monnier
2008-12-08 16:41     ` Eli Zaretskii
2008-12-08 19:36       ` Stefan Monnier
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=200812081531.mB8FVP59017353@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --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.