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.2 - OsoMP_ClosedownFlushes all cached profile data, and closes any open network connection.
Any profile events generated after calling this function may be lost.
While you obviously can call this function at any time, it is highly recommended it only be called during your application's shutdown procedure.
void OsoMP_Closedown( void );
For Windows applications built with Visual Studio, the recommended way to call this function and terminate the process is with this code at the end of the main/WinMain function:
_cexit(); // Call global destructors, and clean up the runtime library. OsoMP_Closedown(); // Flush any lingering profile data, and stop the profiler. ExitProcess( 0 ); // Return control to the OS for final process cleanup. }
If you are building with clang or gcc, you don't need to call this function explicitly. It will be called automatically by the compiler after global destructors have been called. For the curious reader, it is declared as follows for these compilers:
__attribute__((destructor)) void OsoMP_Closedown( void );