unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Memory leaks
Date: Wed, 09 Mar 2011 07:07:57 +0100	[thread overview]
Message-ID: <87zkp4omgy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1Px7S5-0003L3-U9@fencepost.gnu.org> (Richard Stallman's message of "Tue, 08 Mar 2011 19:40:33 -0500")

Richard Stallman <rms@gnu.org> writes:

> Is it possible to write code to record which vectors were consed by
> the operation suspected of having a memory leak?  Then a function to
> call from GDB to test whether a vector are still alive.

It should be possible to record them in a key-weak hashtable.  If they
don't leave after explicitly calling the garbage collector, you've got a
leak.

-- 
David Kastrup



  reply	other threads:[~2011-03-09  6:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03 17:13 Memory leaks Uday S Reddy
2011-03-03 17:55 ` Andreas Schwab
2011-03-03 18:00   ` Uday S Reddy
2011-03-03 23:40     ` Andreas Schwab
2011-03-04 11:39       ` Uday S Reddy
2011-03-04 12:19         ` Eli Zaretskii
2011-03-04 12:59           ` Uday S Reddy
2011-03-07 19:19         ` Uday S Reddy
2011-03-07 20:33           ` Andreas Schwab
2011-03-07 22:27             ` David Kastrup
2011-03-07 22:49               ` David Kastrup
2011-03-09  0:39               ` Richard Stallman
2011-03-07 23:01             ` Uday S Reddy
2011-03-08  2:35               ` Stefan Monnier
2011-03-08  8:57                 ` Andreas Schwab
2011-03-09  0:40                   ` Richard Stallman
2011-03-09  6:07                     ` David Kastrup [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-05 17:17 Daniel Clemente
2009-08-08 18:57 ` Chong Yidong
2009-08-10  8:08   ` Daniel Clemente

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87zkp4omgy.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).