Durk Talsma wrote: > hi, > > While trying to hunt down some memory leaks reported by valgrind, I noticed > that many variables in FGGlobals (which are mainly pointers to many of the > big data structures and subsystem classes) are not deleted upon program exit. > > In most cases adding explicit deletes in ~FGGlobals doesn't seem to hurt. Is > it just an oversight that most of the globals are not deleted or is there is > specific reason? The practical implication of not deleting isn't that bad, > because ~FGGlobals is only called at program exit, after which this memory is > freed anyway. Nevertheless, I'd like to delete these globals, if only to make > valgrind happy. :-)
If memory servers me well I would think those are freed using the atexit() mechanism. It could well be that valgrind doesn't work up to that point to detect it though. Erik ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
