On 10/08/2014, at 3:16 AM, Ryan wrote: > I know; I'm saying this utility manages a private list of objects allocated > using NL_MALLOC. If the object is never free'd, the atexit handler that the > library set up will show the file and line number where the memory was > allocated. Of course, you could set a custom SIGKILL handler that does the > same thing. > > The GC's own malloc wouldn't be replaced. That way, anything that the GC > manages won't be tracked.
Valgrind already does this, in fact it reports the whole stack trace of the function call that allocated the leak. Unfortunately it doesn't show the function arguments. -- john skaller skal...@users.sourceforge.net http://felix-lang.org ------------------------------------------------------------------------------ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
