Pierre-Olivier Gaillard wrote: > I am investigating a memory problem (access to memory that was > released previously) that Purify can't analyze. > > Have you tried libumem (3LIB)? It has special debug options which are designed to catch exactly this kind of problem. Particularly look at umem_debug(3MALLOC).
You should be able to LD_PRELOAD it. Chris > As I don't know the program I am analyzing, I thought I could generate > a big trace of all function calls and search through it. > > The resulting file might be way too big though : I did a trace with > all malloc and free calls and it already takes 155MB. But on the other > hand, if malloc and free represent 1% of all calls I will get a 15GB > trace file which is not that much (I have filled 120GB hard drives > with Linux Trace Toolkit traces and the result was helpful). > > Thanks, > > Pierre-Olivier > > > > > On Nov 7, 2007 1:28 PM, Michael Schuster <[EMAIL PROTECTED]> wrote: > >> Pierre-Olivier Gaillard wrote: >> >>> Thanks a lot. That sounds helpful. >>> How many probes can I have (on a Sparc)? >>> Would a couple millions be OK? >>> >> I can't answer that specific question, but I am wondering what you're >> trying to achieve with the amount of data these probes potentially >> accumulate. >> >> Michael >> -- >> Michael Schuster >> Recursion, n.: see 'Recursion' >> >> > _______________________________________________ > dtrace-discuss mailing list > [email protected] > _______________________________________________ dtrace-discuss mailing list [email protected]
