Свойство | Тип | Описание | |
---|---|---|---|
DepthParsed | int | ||
EntriesParsed | long | ||
Failed | List |
||
HighestFound | |||
PresentInvalid | List |
||
Root |
Свойство | Тип | Описание | |
---|---|---|---|
InlineExtract | long |
Метод | Описание | |
---|---|---|
AddProcess ( |
||
ExtractNextLevel ( |
||
FillPageQueue ( bool OnlyLarge = false ) : int | ||
FillTable ( bool RedundantKernelSpaces, int depth = 4 ) : long | ||
Flatten ( PFN>.Dictionary |
Метод | Описание | |
---|---|---|
InlineExtract ( |
Pretty much not used any more, but I guess I can leave it in for a bit. Trying to decide if I should focus on the core and release a bunch of .csx scripts seems everybody likes scripts these days Or maybe write a UI.... hmmmm An Inline extraction for the page table hierarchy. Why not let the compiler do it? I have code clones here? I guess so, but we can see/deal with the subtle differences at each level here as we implement them. e.g. some levels have LargePage bits and we may also lay over other CPU modes here like 32 in 64 etc..
|
public static AddProcess ( |
||
dp | ||
mem | ||
RedundantKernelEntries | bool | |
DepthToGo | int | |
Результат |
public ExtractNextLevel ( |
||
PageContext | ||
RedundantKernelSpaces | bool | |
Level | int | |
Результат | IEnumerable |
public FillPageQueue ( bool OnlyLarge = false ) : int | ||
OnlyLarge | bool | |
Результат | int |
public FillTable ( bool RedundantKernelSpaces, int depth = 4 ) : long | ||
RedundantKernelSpaces | bool | |
depth | int | |
Результат | long |
public static Flatten ( PFN>.Dictionary |
||
TableEntries | PFN>.Dictionary | |
Level | int | |
Результат | PFN>>.List |
public HARDWARE_ADDRESS_ENTRY,inVtero.net HighestFound | ||
Результат |