pSOSystem System Calls - Read

log_event pROBE+ and ESp System Calls
log_event Logs an event on ESp’s target-resident application monitor, pMONT.
unsigned long log_event (
unsigned long user_event_id, /* user-defined event ID */
unsigned long event_data /* user-defined event data */
)
Description
Arguments
Return Value
Error Codes
Notes
This call logs an event in pMONT’s trace buffer. The log_event() call takes effect
when the ESp data collection run begins.
user_event_id Specifies an ID number for the current call to log_event().
The maximum allowable ID number is 0xff. Providing an ID
number for each call to log_event() helps you keep track of
user-events.
event_data An optional word or words you can use to store data
associated with the event.
This call always returns 0.
None.
Because pMONT uses pSOS+ objects for its functionality, some user-defined entries
in the pSOS+ configuration table affect pMONT behavior and can even increase the
likelihood of error messages. For example, an insufficient number of message
buffers may result in a sudden break in the host/target connection. The paragraphs
that follow explain this.
pMONT uses the system-wide buffer pool to post messages to its queues, so you
need to consider this when specifying kc_nmsgbuf in the pSOS+ configuration
6-6 pSOSystem System Calls