Memory debugger: Difference between revisions

Revision as of 08:31, 27 October 2018

Revision as of 00:55, 16 March 2019

Line 2:

{{Program execution}}

A '''memory debugger''' also known as a '''runtime debugger'''<ref>{{cite journal |last1=Globus |first1=A |last2=Raible |first2=E |date=July 1994 |title=Fourteen ways to say nothing with scientific visualization |url=http://ieeexplore.ieee.org/abstract/document/299418/ |journal= IEEE Computer|volume=27 |issue= 7|pages=86-8886–88 |doi= 10.1109/2.299418|access-date=August 24, 2017 }}</ref> is a [[debugger]] for finding software memory problems such as [[memory leak]]s and [[buffer overflow]]s. These are due to [[Software bug|bugs]] related to the allocation and deallocation of [[dynamic memory]]. Programs written in languages that have [[Garbage collection (computer science)|garbage collection]], such as [[managed code]], might also need memory debuggers, e.g. for memory leaks due to "living" references in collections.

==Overview==