Suppose 1) You are using -dll_prepend <lib> to load a dynamic library
2) Your library is in the stack for a memory leak 3) You use -malloc_test Then you get an SEGV because the static pointer to the __FILE__ and __FUNCT__ in the stack structure are no longer in scope when the malloc log is printed. You can fix the SEGV by moving the library unloading to after the malloc dump. However, it then records that the memory from loading the library is still unfreed. We could tell -malloc_test and friends to ignore that memory. Is this what we should do? Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
