For my project (unrelated to OSG) I prefer to build it on multiple platforms
because the
various compilers catch different set of errors. And also because the most
reliable way to
check memory (errors and leaks) is valgrind under Linux.
Hope it helps
mario
[EMAIL PROTECTED] wrote:
> Hi All,
>
> Appologies for raising this topic again, but I'm starting to loose what
> little hair I have left, over the topic of memory leaks under MS Visual
> Studio C++. I've been working on a project now for 9 months, and finally
> trying to get to a release stage, but on shut down of my application I'm
> getting an immense amount of memory leaks. Now, in the past this forum has
> indicated that this is due to when MS decides to check for memory leaks, and
> that in reality the leaks recorded as being associated with OSG don't really
> occur. Whilst I can accept this in principle, in practice it still leaves
> developers a little short of reliable tools to identify when a leak is really
> a leak.
>
> Can anyone suggest how I can get MS Visual Studio to not report memory leaks
> it believes are associated with OSG ? Alternatively, can anyone suggest how I
> can fix the leak testing to report the correct information ?
>
> Many thanks
>
> Neil.
>
>
> _______________________________________________
> osg-users mailing list
> [email protected]
> http://openscenegraph.net/mailman/listinfo/osg-users
> http://www.openscenegraph.org/
>
--
Ing. Mario Valle
Visualization Group | http://www.cscs.ch/~mvalle
Swiss National Supercomputing Centre (CSCS) | Tel: +41 (91) 610.82.60
v. Cantonale Galleria 2, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
