Table of Contents
1 - Introduction2 - Profiling your application
1 - Integrating the SDK
2 - Initialising the profiler
5 - Event attributes
6 - Defining expressions
3 - User interface reference2 - Initialising the profiler
3 - Profile events
4 - Block types5 - Event attributes
6 - Defining expressions
4 - SDK Reference
Contact Information
Sales
Sales and licensing related questions should be sent to our sales team at:Feedback
If you have feedback regarding this website or any of our products, please use the following email address:Support
Questions related to problems you have encountered with either this website or any of our products should be directed to our support team at:Enquiries
Any other questions, or general enquiries should be sent to the following email address:2.3 - Profile events
While memory profiles can contain a lot of information, nearly all of that ancilliary data goes to supporting profile events. Profile events are records of actual actions performed by your application with regards to allocating and freeing memory, and messages that you can insert to help give context to the events around them.This page will discuss each profile event type in turn:
Allocation Events | When your application allocates a piece of memory from the heap - or any other resource that you want to profile - it should generate an allocation event by calling OsoMP_Allocate. |
Free Events | Free events are the companions of allocations. When a previously allocated piece of memory, or resource is freed, a free event should be generated by calling OsoMP_Free. |
Messages |
As mentioned at the top of this page, messages can be inserted (programmatically) anywhere within a memory profile to help provide additional context
as to what an application is doing at any given time. Messages can be inserted into a profile through a call to OsoMP_Message. |
Message events, on the other hand, have their own unique colours passed directly to the OsoMP_Message function.
All events can also have application defined attributes attached, which can be used to evaluate custom warning and error expressions.