From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] leak
Date: Thu, 15 Sep 2005 17:11:55 +0100 [thread overview]
Message-ID: <80d94519d359c029b3958f075b9c5660@terzarima.net> (raw)
In-Reply-To: <200509151601.j8FG12K29865@zamenhof.cs.utwente.nl>
> Is there an easy way to record (get at) the whole
> function call stack at the moment of allocation
> (e.g. like purify gives)?
there was an older acid leak detection library that
took a snapshot of the call stack on each allocation.
that was useful, as you say.
prev parent reply other threads:[~2005-09-15 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 18:23 Steve Simon
2005-08-24 18:46 ` Sape Mullender
2005-09-15 16:01 ` Axel Belinfante
2005-09-15 16:06 ` Russ Cox
2005-09-16 11:29 ` Axel Belinfante
2005-09-16 14:16 ` Russ Cox
2005-09-15 16:11 ` Charles Forsyth [this message]
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=80d94519d359c029b3958f075b9c5660@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).