To identify the callback on which the manipulation is done, the user has to provide the API function with a PIN_CALLBACK object. This PIN_CALLBACK object is returned from any of the callback registering functions (e.g. PIN_AddFiniFunction ()) as a return value.
◆ PIN_CALLBACK
Container for a PIN callback
◆ CALLBACK_GetExecutionOrder()
Gets the execution order of a registered callback function. See CALL_ORDER. The the lower the order, the sooner it will be called relative to other similar callbacks
- Parameters
-
callback | Registered Callback function returned from *_Add*Function() |
- Returns
- CALL_ORDER The current order value of the callback
- Availability:
- Mode: JIT
O/S: Linux, Windows & macOS*
CPU: All
◆ CALLBACK_SetExecutionOrder()
Sets the execution order of a registered callback function. See CALL_ORDER. The the lower the order, the sooner it will be called relative to other similar callbacks.
- Parameters
-
callback | Registered Callback function returned from *_Add*Function() |
order | New order to assign to the callback (relative to the other callbacks). See CALL_ORDER for usage details.
|
- Note
- The pin client lock is obtained during the call of this API.
- Availability:
- Mode: JIT
O/S: Linux, Windows & macOS*
CPU: All
◆ PIN_CALLBACK_INVALID()
Invalid value for PIN callback