Thanks Joshua. I am trying valgrind as well. However that requires us to run our server for a long time before we can even simulate the memory leak. I am also trying to use google perftools. Dehydra is another approach. I had assumed that script for detecting memory leak would be one of the first scripts that would be available for a static analyzer, especially since one of Taras's old blogs was about porting UNO into dehydra. I also see that there is a bug https://bugzilla.mozilla.org/show_bug.cgi?id=526309
for this (Basic Check for memory leaks). however not sure if the attached script against that bug does work as expected. I'll anyway check. is there anything else that already exists in Dehydra that I can try towards detecting memory leaks? Thanks Harsha On Sep 4, 11:24 pm, Joshua Cranmer <[email protected]> wrote: > On 09/04/2010 12:31 PM, Harsha wrote:> We have finally got dehydra > installed. Are there any java scripts that > > I can use to detect memory leaks in our largely C (some C++) code base > > of about 300k lines? > > I don't know the state of the art in static memory leak detection, but > you are likely to find that valgrind and its ilk are a more useful tool > for tracking down memory leaks than dehydra, unless you have a > well-defined pointer ownership model. > > > Under Dehydra FAQ we have "Where can I find JS code for real-life > > analyses for dehydra?". However I cannot find any scripts in that > > link. Can somebody please point me to some analysis scripts so that I > > play with it and familiarize myself in using dehydra to solve my > > problem - detect memory leaks and fix them > > http://mxr.mozilla.org/mozilla-central/source/js/src/jsstack.jsis one > script.http://mxr.mozilla.org/mozilla-central/source/xpcom/analysis/is a whole > suite of scripts. _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
