Hi Rob,

I can quickly outline in "pseudo-code":

Lets say I have the following wrappers

size_t zmalloc(size_t howmuch) {
return(malloc(howmuch));
}

void zfree(size_t adr) {
return(free(adr));
}

I do this so that I could replace malloc and free with some other allocaters later if required.. like tcmalloc... however that doesn't mean that it is a memory leak its only if the code that uses it doesn't handle it properly.

Now I have some custom module

void newFoo(foo** f) {
*f = (foo*)zmalloc(sizeof(foo));
*f->bar = 324.35;
}

void freeFoo(foo** f) {
zfree(*f);
*f = NULL;
}

As a last step I have a main function:

int main(....) {
foo* f;

newFoo(&f);

// memory leak

return(0);

}

Now what I would expect in the report is not just the pointer to the code in the wrapper but rather, bubbling up the whole call-stack and report newFoo(&f) in the main() method as the root-cause of the leak..

Valgrind can do this in Linux without problems.. so I'm wondering whether Inspector could be configured to do so as well?

Thanks,
Christian

Hi Rob,

Thanks for the hint, afterall it seems that it was quite a stupid question... sorry about that.

Christian