diff options
author | Jan Kotas <jkotas@microsoft.com> | 2017-05-17 18:25:05 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-05-17 18:25:05 -0700 |
commit | 13e7c4368da664a8b50228b1a5ef01a660fbb2dd (patch) | |
tree | f3f36157c201fab5bc4558beceb9f8e83fbab3f6 /src/vm/frames.h | |
parent | c290deb3bd5331a5d70470e6203f2b4b2059bd90 (diff) | |
download | coreclr-13e7c4368da664a8b50228b1a5ef01a660fbb2dd.tar.gz coreclr-13e7c4368da664a8b50228b1a5ef01a660fbb2dd.tar.bz2 coreclr-13e7c4368da664a8b50228b1a5ef01a660fbb2dd.zip |
Finish deleting dead CAS code from CoreLib (#11436)
Fixes #9321 and deletes CleanupToDoList.cs
Delete unmanaged security implementation
Diffstat (limited to 'src/vm/frames.h')
-rw-r--r-- | src/vm/frames.h | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/src/vm/frames.h b/src/vm/frames.h index d7daa7649b..108f9f792c 100644 --- a/src/vm/frames.h +++ b/src/vm/frames.h @@ -137,8 +137,6 @@ // | // | // +-ExceptionFilterFrame - this frame wraps call to exception filter -// | -// +-SecurityContextFrame - place the security context of an assembly on the stack to ensure it will be included in security demands // //------------------------------------------------------------------------ #if 0 @@ -260,7 +258,6 @@ FRAME_TYPE_NAME(ExceptionFilterFrame) #if defined(_DEBUG) FRAME_TYPE_NAME(AssumeByrefFromJITStack) #endif // _DEBUG -FRAME_TYPE_NAME(SecurityContextFrame) #undef FRAME_ABSTRACT_TYPE_NAME #undef FRAME_TYPE_NAME @@ -3495,29 +3492,6 @@ public: GSCookie * GetGSCookiePtr() { LIMITED_METHOD_CONTRACT; return &m_gsCookie; } }; - -// The frame doesn't represent a transition of any sort, it's simply placed on the stack to represent an assembly that will be found -// and checked by stackwalking security demands. This can be used in scenarios where an assembly is implicitly controlling a -// security sensitive operation without being explicitly represented on the stack. For example, an assembly decorating one of its -// classes or methods with a custom attribute can implicitly cause the ctor or property setters for that attribute to be executed by -// a third party if they happen to browse the attributes on the assembly. -// Note: This frame is pushed from managed code, so be sure to keep the layout synchronized with that in -// bcl\system\reflection\customattribute.cs. -class SecurityContextFrame : public Frame -{ - VPTR_VTABLE_CLASS(SecurityContextFrame, Frame) - - Assembly *m_pAssembly; - -public: - virtual Assembly *GetAssembly() { LIMITED_METHOD_CONTRACT; return m_pAssembly; } - - void SetAssembly(Assembly *pAssembly) { LIMITED_METHOD_CONTRACT; m_pAssembly = pAssembly; } - - // Keep as last entry in class - DEFINE_VTABLE_GETTER_AND_CTOR_AND_DTOR(SecurityContextFrame) -}; - //------------------------------------------------------------------------ // These macros GC-protect OBJECTREF pointers on the EE's behalf. // In between these macros, the GC can move but not discard the protected |