About Memory Profiling for C and C++

Memory Profiling for C and C++

Run-time memory errors and leaks are among the most difficult errors to locate and the most important to correct. The symptoms of incorrect memory use are unpredictable and typically appear far from the cause of the error. The errors often remain undetected until triggered by a random event, so that a program can seem to work correctly when in fact it's only working by accident.

That's where the Memory Profiling feature can help you.

Memory Profiling uses Source Code Insertion Technology for C and C++.

Because of the different technologies involved, Memory Profiling for Java is covered in a separate section.

Memory Profiling for C and C++ supports the following languages:

How Memory Profiling for C and C++ Works

When an application node is executed, the source code is instrumented by the C or C++ Instrumentor (attolcpp or attolcc1). The resulting source code is then executed and the Memory Profiling feature outputs a static .tsf file for each instrumented source file and a dynamic .tpf file.

These files can be viewed and controlled from the OneTest Embedded GUI. Both the .tsf and .tpf files need to be opened simultaneously to view the report.

Of course, these steps are mostly transparent to the user when the test or application node is executed in the OneTest Embedded GUI or Eclipse (for C and C++).

 

To learn about

See

Performing Memory Profiling on C and C++ source code

Using Runtime Analysis Features

How Memory Profiling for C and C++ works

Memory Profiling User in C and C++

Source Code Insertion technology

Source Code Insertion Technology

JVMPI technology for Java memory analysis

JVMPI Technology

Understanding Memory Profiling Reports

Memory Profiling Results

Using the Memory Profiler Viewer

Using the Memory Profiling Viewer

Customizing the Memory Profiling Viewer

Memory Profiling Viewer Preferences

 

Related Topics

Memory Profiling SettingsRuntime AnalysisMemory Profiling for Java