You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.
Any differences in how handles should be interpreted (no indirection, single indirection, double indirection) is already abstracted via InfoAccessType enum. When we get a handle from the CLR we also get an InfoAccessType value:
// Can a value be accessed directly from JITed code.
enum InfoAccessType
{
IAT_VALUE, // The info value is directly available
IAT_PVALUE, // The value needs to be accessed via an indirection
IAT_PPVALUE // The value needs to be accessed via a double indirection
};
We need to make sure the existing code is correct for the new codepaths.
The text was updated successfully, but these errors were encountered:
Any differences in how handles should be interpreted (no indirection, single indirection, double indirection) is already abstracted via InfoAccessType enum. When we get a handle from the CLR we also get an InfoAccessType value:
// Can a value be accessed directly from JITed code.
enum InfoAccessType
{
IAT_VALUE, // The info value is directly available
IAT_PVALUE, // The value needs to be accessed via an indirection
IAT_PPVALUE // The value needs to be accessed via a double indirection
};
We need to make sure the existing code is correct for the new codepaths.
The text was updated successfully, but these errors were encountered: