From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <26c8145b85f3393b89c8032d5e5c4766@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Mon, 22 Feb 2010 17:43:50 +0000
To: 9fans@9fans.net
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] leak(1) problem
Topicbox-Message-UUID: d81b4476-ead5-11e9-9d60-3106f5b1d025

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