Never mind... I see it. It's the _n_objects++ in the constructor of ReferenceCounter. This happens despite using --disable-reference-counting...
So now my question is... should it? Should we turn off doing that ++ and -- in Reference counter if you specifically disable reference counting? Or should we just disable printing any messages about memory leaks if you disable reference counting. I guess what I'm getting at here is that I want that message to go away... and NEVER be shown. There should be an option for that.... Any ideas? Derek On Feb 3, 2010, at 1:26 PM, Derek Gaston wrote: > Yo. > > So... I'm trying to turn off reference counting with > --disable-reference-counting... but I'm still getting "Memory Leak Detected!" > errors at the end of my run. > > Besides the obvious "Fix the memory leak!"... is there something else I need > to do to make this message go away? I really don't understand how it can be > getting to this point if I've disabled reference counting. > > Any quick ideas before I really start digging into this? > > Derek ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
