search

gkb / googletest

Automatically exported from code.google.com/p/googletest
0 stars 0 forks source link

Memory leak detection #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
There doesn't seem to be good memory leak detection (or any at all). 
What would be nice is if there's a way to save the heap and stack memory
address before the test, and then compare the heap and stack memory
addresses after end of the test fixture and check for any memory leaks.
This doesn't seem to be happening.

Original issue reported on code.google.com by ray...@gmail.com on 17 Jul 2008 at 8:35

GoogleCodeExporter commented 9 years ago

Original comment by shiq...@gmail.com on 31 Jul 2008 at 6:43

GoogleCodeExporter commented 9 years ago 
There's no portable way to do it, so we'll have to write different solutions on
different platforms.  We don't have the resources for this at this time.  Some
volunteers should take the initiative if they want this to happen.

Original comment by shiq...@gmail.com on 5 Aug 2008 at 7:17

GoogleCodeExporter commented 9 years ago

Original comment by shiq...@gmail.com on 17 Sep 2008 at 9:49