Editing Debugger (section)

==={{anchor|Reverse debugging}}Reverse debugging===
<!-- At least six pages redirect to this section. Please do not remove the section or rename the anchor, without first getting consensus on the talk page. -->
Some debuggers include a feature called "'''reverse debugging'''", also known as "historical debugging" or "backwards debugging". These debuggers make it possible to step a program's execution backwards in time. Various debuggers include this feature. [[Microsoft Visual Studio]] (2010 Ultimate edition, 2012 Ultimate, 2013 Ultimate, and 2015 Enterprise edition) offers IntelliTrace reverse debugging for C#, Visual Basic .NET, and some other languages, but not C++. Reverse debuggers also exist for C, C++, Java, Python, Perl, and other languages. Some are open source; some are proprietary commercial software. Some reverse debuggers slow down the target by orders of magnitude, but the best reverse debuggers cause a slowdown of 2× or less. Reverse debugging is very useful for certain types of problems, but is still not commonly used yet.<ref>{{cite web|author1=Philip Claßen|author2=Undo Software|title=Why is reverse debugging rarely used?|url=http://programmers.stackexchange.com/questions/181527/why-is-reverse-debugging-rarely-used|work=Programmers Stack Exchange|publisher=Stack Exchange, Inc|access-date=12 April 2015}}</ref>