From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] leak
Date: Thu, 15 Sep 2005 18:01:01 +0200 [thread overview]
Message-ID: <200509151601.j8FG12K29865@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 24 Aug 2005 14:46:47 -0400." <a06f3a65eaa6cde45a9234929df4c640@plan9.bell-labs.com>
> > Used leak(1) in anger for the first time,
> > major kudos to its author.
>
> Our resident genius Russ.
>
> Leak: can't live without it.
having been using it a bit today I'm
wondering if I'm missing something.
Is there an easy way to record (get at) the whole
function call stack at the moment of allocation
(e.g. like purify gives)?
Right now I just see the immediate caller of malloc
which may be a bit too limited (cumbersome to work with)
at times.
I've been adding 'setmalloctag(x, getcallerpc(&foo))'
by hand in the source to slowly get to the caller
of the caller of (the caller of ...) of malloc
and could imagine there is a better way... ?
Axel. - nevertheless, found+plugged the leaks :-)
next prev parent reply other threads:[~2005-09-15 16:01 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 [this message]
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
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=200509151601.j8FG12K29865@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).