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

Reply via email to