Test run details will be shown in the AnalyzeTool view automatically after the data capture in tracing utility connection. You can also open the memory analysis data file by yourself later. For more information, see AnalyzeTool files.
+
There are two options for opening a memory analysis data file:
+
+
From Project pop-up menu, select AnalyzeTool > Open and analyze data file
+
In the AnalyzeTool view, select Open and analyze data file
+
+
The memory leak analysis results are displayed in the AnalyzeTool window. Test runs with the memory leak information is displayed in the left pane. The right pane shows the information on the selected memory leak call stack.
+
+
+
Description of call stack view
+
+
One line always contains the memory address, for example 7cf255571 MemoryLeaker.exe. A module name is displayed if the memory address is in the module memory area, otherwise ??? is displayed.
+
The function name, for example CMemoryLeakerListbox: :OfferKeyEventL, is displayed if the function is identified, otherwise ??? is displayed. The class name is also displayed if the function belongs to a class.
+
A .cpp file name, for example MemoryLeakerListbox.cpp:570, is displayed if the source code file is available. If the address can be matched to an exact code line, the line number is shown. Code line number is ??? if the memory address is within function memory area but does not point to a code line.
+
By double-clicking the call stack item which has known code line number opens the appropriate source code file to that code line.
+
+
Descriptions of icons
+
+
() Describes that the module belongs to an active/selected project and has been built with AnalyzeTool. The module can be analyzed right away.
+
() Describes that the module belongs to an active/selected project but has not been built with AnalyzeTool. It is possible to analyze the project but it needs to be built first.
+
() Describes that the module does not belong to an active/selected project. It is some library that has been loaded but is not available in the Carbide.c++ project at the moment. You need to take additional steps (identifying component, importing to Carbide.c++, building with AnalyzeTool etc.) for being able to analyze.
+
+
) Describes that the module belongs to an active/selected project and has been built with AnalyzeTool. The module can be analyzed right away.
) Describes that the module belongs to an active/selected project but has not been built with AnalyzeTool. It is possible to analyze the project but it needs to be built first.
) Describes that the module does not belong to an active/selected project. It is some library that has been loaded but is not available in the Carbide.c++ project at the moment. You need to take additional steps (identifying component, importing to Carbide.c++, building with AnalyzeTool etc.) for being able to analyze.