From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] leak(1) problem
Date: Mon, 22 Feb 2010 17:43:50 +0000 [thread overview]
Message-ID: <26c8145b85f3393b89c8032d5e5c4766@quintile.net> (raw)
I have a memory leak in my code, and am using leak(1) to track
it but I have reached an en-passe.
Leak only reports strdup(2) as being the source of the leak. I added
a setmalloctag(2) call directly after the call to strdup(2) but
leak continues to report the strdup(2) address rather than its
bounding function.
Is this expected or have I done something silly?
-Steve
next reply other threads:[~2010-02-22 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 17:43 Steve Simon [this message]
2010-02-22 18:01 ` Russ Cox
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=26c8145b85f3393b89c8032d5e5c4766@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).