[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Memory leaks
From: |
Richard Stallman |
Subject: |
Re: Memory leaks |
Date: |
Tue, 08 Mar 2011 19:40:33 -0500 |
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.
After you find one, you could do a GC with a conditional breakpoint
to stop when that vector is marked. Then you would see exactly
what is keeping it alive. If you do this for each vector that was
consed during the operation in question, you will eventually find
one that was expected to be GC'd, and find the bug.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org, www.gnu.org
- Re: Memory leaks, (continued)
- Re: Memory leaks, Uday S Reddy, 2011/03/07
- Re: Memory leaks, Andreas Schwab, 2011/03/07
- Re: Memory leaks, David Kastrup, 2011/03/07
- Re: Memory leaks, David Kastrup, 2011/03/07
- Re: Memory leaks, Richard Stallman, 2011/03/08
- Re: Memory leaks, Uday S Reddy, 2011/03/07
- Re: Memory leaks, Stefan Monnier, 2011/03/07
- Re: Memory leaks, Andreas Schwab, 2011/03/08
- Re: Memory leaks,
Richard Stallman <=
- Re: Memory leaks, David Kastrup, 2011/03/09