From: Abhijeet More <abhijeet.more@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
guile-user@gnu.org,
"Tibi Turbureanu" <tiberiuturbureanu@gmail.com>
Subject: Re: Possible Memory Leak with stream-for-each
Date: Sat, 31 Jul 2010 16:16:53 -0400 [thread overview]
Message-ID: <AANLkTikf5ERjsSAaA_SCkm9Hdq1Smb8m0D968bv1cVUp@mail.gmail.com> (raw)
In-Reply-To: <m3iq3vg9dg.fsf@unquote.localdomain>
On Sat, Jul 31, 2010 at 7:48 AM, Andy Wingo <wingo@pobox.com> wrote:
[snip]
> 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.
[snip]
Andy,
Thanks! That's a great answer!
I'll see what I can do with these guidelines.
Abhijeet
next prev parent reply other threads:[~2010-07-31 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 18:08 Possible Memory Leak with stream-for-each Abhijeet More
2010-07-20 20:36 ` Andy Wingo
2010-07-21 7:00 ` Tristan Colgate
2010-07-24 16:13 ` Ludovic Courtès
2010-07-24 16:32 ` Abhijeet More
2010-07-24 16:46 ` Abhijeet More
2010-07-26 9:36 ` Andy Wingo
2010-07-30 0:38 ` Abhijeet More
2010-07-31 11:48 ` Andy Wingo
2010-07-31 20:16 ` Abhijeet More [this message]
2010-08-11 16:57 ` Abhijeet More
2010-08-02 3:29 ` Tibi Turbureanu
2010-08-15 15:12 ` Heap profiler Ludovic Courtès
2010-09-02 12:49 ` Possible Memory Leak with stream-for-each Ludovic Courtès
2010-09-02 16:20 ` Julian Graham
2010-09-02 18:46 ` Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikf5ERjsSAaA_SCkm9Hdq1Smb8m0D968bv1cVUp@mail.gmail.com \
--to=abhijeet.more@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=tiberiuturbureanu@gmail.com \
--cc=wingo@pobox.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.
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).