📄️ Code Paths
A lot of the detail you see in CodeGlass comes from something called code paths.
📄️ Context Menus
In the CodeGlass Client there are a lot of places where Code Members and Memory Objects are shown.
📄️ Data Sources
CodeGlass groups all data collected for a single instance in something called a data source. A data source can be seen as a self contained container containing profiling data. Every application instance has at least 1 data source. This is the main data source.
📄️ Dump Files
Sometimes you want to collect profiling data on a different device than that you want to analyze it, or you might want share your findings with a coworker. To make this process as simple as possible, CodeGlass allows users to export all their data to a CodeGlass dump file.
📄️ Filters
The goal of filters is to allow the user to specify which functions CodeGlass should profile.
📄️ Julia Type Severity
In Julia you usually do not need to declare types for every value. The compiler tries to infer types based on how values are used in the code. In many cases this works well and results in efficient compiled code.
📄️ Pause Data Collection
CodeGlass works by adding and listening to callbacks that are added during compile time. This allows CodeGlass to efficiently get informed about events that happen in the code, like a function call or a memory allocation.