Jump to content

KernRASSysTrace: Difference between revisions

From EDM2
No edit summary
Ak120 (talk | contribs)
mNo edit summary
Line 2: Line 2:


==Synopsis==
==Synopsis==
APIRET APIENTRY KernRASSysTrace(ULONG major,ULONG minor,PVOID buf, ULONG size);
APIRET APIENTRY KernRASSysTrace (ULONG major, ULONG minor, PVOID buf, ULONG size);


==Parameters==
==Parameters==
; major :     Major number of RAS event  
;major: Major number of RAS event
; minor :   Minor number of RAS event  
;minor: Minor number of RAS event
; buf :     buffer to be added to the RAS log  
;buf: buffer to be added to the RAS log
; size :     size of the buffer  
;size: size of the buffer


==Comments==
==Comments==
This is not explained in the PDD reference manual, but in the debug handbook IIRC. Warning: The buffer is assumed to be allocated on the task stack, not as a global variable or a VMAlloc'd memory area.  
This is not explained in the PDD reference manual, but in the debug handbook IIRC. Warning: The buffer is assumed to be allocated on the task stack, not as a global variable or a VMAlloc'd memory area.


[[Category:KEE]]
[[Category:KEE]]

Revision as of 12:33, 19 July 2020

This is the equivalence of the DevHlp_RASTrace function.

Synopsis

APIRET APIENTRY KernRASSysTrace (ULONG major, ULONG minor, PVOID buf, ULONG size);

Parameters

major
Major number of RAS event
minor
Minor number of RAS event
buf
buffer to be added to the RAS log
size
size of the buffer

Comments

This is not explained in the PDD reference manual, but in the debug handbook IIRC. Warning: The buffer is assumed to be allocated on the task stack, not as a global variable or a VMAlloc'd memory area.