Memory debugger: Difference between revisions

Revision as of 16:11, 24 August 2017

Revision as of 16:19, 24 August 2017

Line 9:

As abnormally high memory utilization can be a contributing factor in [[software aging]], memory debuggers can help programmers to avoid [[software anomaly|software anomalies]] that would exhaust the computer system memory, thus ensuring high reliability of the software even for long [[run time (program lifecycle phase)|runtimes]].

==Comparison to static analyzer==

Some [[List of tools for static code analysis|static analysis tools]] can also help find memory errors. Memory debuggers operate as part of an application while it's [[Execution (computing)|running]] while [[static code analysis]] is performed by analyzing the code without executing it. These different techniques will typically find different instances of problems, and using them both together yields the best result.<ref>{{cite web|url=https://software.intel.com/en-us/inspector-user-guide-windows-dynamic-analysis-vs-static-analysis|access-date=August 24, 2017|title=Dynamic Analysis vs. Static Analysis}}</ref>

==List of memory debugging tools==

This is a list of [[Programming tool|tools]] useful for memory debugging. A [[profiling (computer programming)|profiler]] can be used in conjunction with a memory debugger. Some [[static code analysis]] [[List of tools for static code analysis|tools]] can also help find memory errors.

{|class="wikitable sortable"