Tizen Native API
3.0
|
The T-trace API provides functions for writing trace message to the system trace buffer.
Required Header
#include <trace.h>
Overview
The T-trace API provides functions for writing trace event to the system trace buffer. By using T-trace tool, These events can be displayed with T-trace event from Tizen framework.
For more information on features, see T-trace User Guide and T-Trace Tutorial.
Functions | |
void | trace_begin (const char *name,...) |
Writes a trace event to indicate that a synchronous event has begun. | |
void | trace_end () |
Writes a trace event to indicate that the synchronous event has ended. | |
void | trace_async_begin (int cookie, const char *name,...) |
Writes a trace event to indicate that an asynchronous event has begun. | |
void | trace_async_end (int cookie, const char *name,...) |
Writes a trace event to indicate that the asynchronous event has ended. | |
void | trace_update_counter (int value, const char *name,...) |
Writes a trace event to track change of integer counter. |
Enumeration Type Documentation
enum trace_error_e |
Function Documentation
void trace_async_begin | ( | int | cookie, |
const char * | name, | ||
... | |||
) |
Writes a trace event to indicate that an asynchronous event has begun.
- Since :
- 2.3.2
- Remarks:
- The specific error code can be obtained using the get_last_result() method. Error codes are described in Exception section.
- Parameters:
-
[in] cookie An unique identifier for distinguishing simultaneous events [in] name The name of event (optionally containing format specifiers)
- Exceptions:
-
TRACE_ERROR_NONE Success TRACE_ERROR_IO_ERROR I/O error
- See also:
- trace_async_end()
void trace_async_end | ( | int | cookie, |
const char * | name, | ||
... | |||
) |
Writes a trace event to indicate that the asynchronous event has ended.
- Since :
- 2.3.2
- Remarks:
- trace_async_end() ends matched trace_async_begin() which has same cookie and name.
- The specific error code can be obtained using the get_last_result() method. Error codes are described in Exception section.
- Parameters:
-
[in] cookie An unique identifier for distinguishing simultaneous events [in] name The name of event (optionally containing format specifiers)
- Exceptions:
-
TRACE_ERROR_NONE Success TRACE_ERROR_IO_ERROR I/O error
- See also:
- trace_async_begin()
void trace_begin | ( | const char * | name, |
... | |||
) |
Writes a trace event to indicate that a synchronous event has begun.
- Since :
- 2.3.2
- Remarks:
- The specific error code can be obtained using the get_last_result() method. Error codes are described in Exception section.
- Parameters:
-
[in] name The name of event (optionally containing format specifiers)
- Exceptions:
-
TRACE_ERROR_NONE Success TRACE_ERROR_IO_ERROR I/O error
- See also:
- trace_end()
void trace_end | ( | ) |
Writes a trace event to indicate that the synchronous event has ended.
- Since :
- 2.3.2
- Remarks:
- trace_end() ends the most recently called trace_begin().
- The specific error code can be obtained using the get_last_result() method. Error codes are described in Exception section.
- Exceptions:
-
TRACE_ERROR_NONE Success TRACE_ERROR_IO_ERROR I/O error
- See also:
- trace_begin()
void trace_update_counter | ( | int | value, |
const char * | name, | ||
... | |||
) |
Writes a trace event to track change of integer counter.
- Since :
- 2.3.2
- Remarks:
- The specific error code can be obtained using the get_last_result() method. Error codes are described in Exception section.
- Parameters:
-
[in] value The counter value [in] name The name of event (optionally containing format specifiers)
- Exceptions:
-
TRACE_ERROR_NONE Success TRACE_ERROR_IO_ERROR I/O error