Skip to content

Latest commit

 

History

History
93 lines (61 loc) · 3 KB

profiler.md

File metadata and controls

93 lines (61 loc) · 3 KB

NOTE: This page is referenced from README.md. to describe source-code profiler tools which count the number of times each function or method was executed, and also the amount of memory used.

Such tools for developers usually specialize on a particular programming languge and IDE:

Profilers are also offered by proprietary APM (Application Performance Monitoring) tool vendors:

## Debugging vs. Profiling

Debugging is looking for logical errors in programming code rather than resources that the program consumes, which what profilers measure.

## Troubleshooting vs Profiling

An example of troubleshooting is analyzing dump files Windows automatically saves after a "blue screen of death" occurs after a crash; whereas profiling is analyzing programming code while it executes.

Within Archives at https://dev.windows.com/en-us/downloads/sdk-archive

  • http://msdn.microsoft.com/en-US/windows/desktop/bg162891 Windows Software Development Kit for Windows 8.1 installs a choice of several components:

  • Windows Software Development Kit

  • Windows Performance Toolkit

  • Debugging Tools for Windows

  • Application Verifier for Windows

  • .NET Framework 4.5.1 Software Development Kit

  • Windows App Certification Kit

  • MSI Tools

Blue screen memory dumps are stored in C:\Windows\Minidumps

  • .symfix to setup symbols from Microsoft's servers.
  • .bugcheck to display codes
  • .hh for help
## Profiling ## Resources