[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possible Memory Leak with stream-for-each

From: Abhijeet More
Subject: Re: Possible Memory Leak with stream-for-each
Date: Sat, 31 Jul 2010 16:16:53 -0400

On Sat, Jul 31, 2010 at 7:48 AM, Andy Wingo <address@hidden> wrote:


> To really track this down we need a heap profiler. To make a heap
> profiler, we need to hack libgc. libgc has some of the things we need
> already, but some are only present in debug builds, which is
> ridiculous -- one should always have the ability to profile the heap. We
> need to figure out which value is being misidentified as a pointer to a
> heap-allocated stream-pair.
> That is my analysis anyway. The next step is to be able to expose the
> back-pointer graph from libgc, and write analysis tools to figure out
> which non-stream objects point to a stream.


Thanks! That's a great answer!
I'll see what I can do with these guidelines.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]