Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This function is called by the kernel whenever an event occurs that can be logged.
Syntax
void CeLogData( BOOL fTimeStamp, WORD wID, PVOID pData, WORD wLen, DWORD dwZoneUser, DWORD dwZoneCE, WORD wFlag, BOOL fFlagged ); |
Parameters
- fTimeStamp
-
[in] Identifies whether a time stamp is needed. When set to TRUE, a time stamp is needed to coincide with the logged event.
- wID
-
[in] Identifier of the event that has occurred.
For more information about events, see CeLog Event Identifiers.
- pData
-
[in] Pointer to a buffer that contains the data of the logged event.
- wLen
-
[in] Length of data pointed to by pData. Each event can have a differently sized structure.
- dwZoneUser
-
[in] User-defined zone. OEMs can create their own zones to track events.
- dwZoneCE
-
[in] Zone of the event that was logged and identified by wID.
For more information about zones, see CeLog Zones.
- wFlag
-
[in] User-defined flag.
- fFlagged
-
[in] Indicates whether to use the user-defined flag, wFlag.If set to TRUE, wFlaghas been specified. If set to FALSE, wFlagis ignored.
Return Value
None.
Remarks
Since an attacker could load celog.dll onto a retail device and start getting data, do not log secret information to CeLog.
Requirements
Header | celog.h |
Library | coredll.lib |
Windows Embedded CE | Windows CE 3.0 and later |
Windows Mobile | Windows Mobile Version 5.0 and later |