Trees | Indices | Help |
|
---|
|
object --+ | list --+ | MonitorProcessLog
Yields each API call event to the parent handler. Optionally it may beautify certain API calls.
|
|||
new empty list |
|
||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from Inherited from |
|
|||
Inherited from |
|
|||
Inherited from |
|
x.__init__(...) initializes x; see help(type(x)) for signature
|
Keep track which function has which function index. This informational call is omitted from the actual logs. |
iter(x)
|
Required for the JSON reporting module as otherwise the on-demand generated list of API calls would be seen as empty. Note that the result structure is kept between processing and reporting time which means that at reporting time, where this functionality is actually needed, the has_apicalls will already have been set while iterating through the BSON logs iterator in the parse() function of the WindowsMonitor class. We use this knowledge to pass along whether or not this log actually has API call events and thus whether it's "nonzero" or not. (The correctness of this field is required as otherwise the json.dump() function will fail - probably due to buffering issues). |
Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Fri Nov 4 23:21:58 2016 | http://epydoc.sourceforge.net |