Profiling Visual C++ Programs

Related Topics

This section of the Quantify help system gives you specific information and instructions for profiling Visual C++ programs.

To learn about

See

How you can use Quantify with Visual C++ native-code programs

About Profiling Visual C++ Programs

Instructions for profiling C++ programs in the Quantify standalone user interface

Profiling Visual C++ Programs with Quantify Standalone

Instructions for profiling C++ programs the from the command line

Profiling Visual C++ Programs from the Command Line

How to get line level performance data when you profile the release version of a program

Profiling the Release Version of Visual C++ Programs

How to run a child process under Quantify

Profiling Child Processes

How to run a system service under Quantify

Profiling Visual C++ System Services

How to run an in-proc COM server under Quantify

Profiling In-proc COM Servers

How to run an out-of-proc COM server under Quantify

Profiling Out-of-proc COM Servers

Saving time when your program runs under Quantify by instrumenting modules in advance

Preinstrumenting Modules

Changing the default file name for the instrumented version of a program

Changing the File Name of Instrumented Programs

Changing the default directory for caching instrumented versions of programs

Changing the Cache Directory for Instrumented Programs

Checking information logged for the run of a program under Quantify

Viewing Log Information

The role of debug data in profiling C++ programs

How Quantify Uses Visual C++ Debug Data

The locations where Quantify can find debug data for C++ programs

How Quantify Locates Visual C++ Debug Data

(C) Copyright IBM Corporation 1993, 2009.