Table of Contents1 - Introduction
2 - Profiling your application
3 - User interface reference
4 - SDK Reference
SalesSales and licensing related questions should be sent to our sales team at:
FeedbackIf you have feedback regarding this website or any of our products, please use the following email address:
SupportQuestions related to problems you have encountered with either this website or any of our products should be directed to our support team at:
EnquiriesAny other questions, or general enquiries should be sent to the following email address:
4.5 - OsoMP_InitialiseInitialises the Oso Memory Profiler SDK.
void OsoMP_Initialise( const char* filename, const char* hostname, UInt16 port, UInt32 sessionid );
Specifies the name of a file to which profile data will be saved.|
The filename is not modified in any way. It can be an absolute path, relative path, or any network share that your application can access through fopen.
If local profiling is not required, this parameter can be NULL.
The network name of a machine that is running an instance of the Oso Memory Profiler.|
Providing a valid hostname and port will initialise the profiler for remote profiling. Profile data will be sent directly to the Oso Memory Profiler running on the specified host.
If remote profiling is not required, this parameter can be NULL.
Port number on which to connect to the Oso Memory Profiler.|
The default port number is defined in OsoMemoryProfiler.h as OSOMP_PortNumber. This can be changed, however, in the Oso Memory Profiler preferences dialog.
Application defined session identifier. Session identifiers should be unique on a per-application basis.|
The Oso Memory Profiler can close sessions automatically when a new session with a matching identified connects or is loaded. If this functionality is not required, this parameter can be 0.
Future versions of the Oso Memory Profiler might use the session identifiers for more advanced features.