-
1a9b61d2
by Zhiyi Zhang at 2025-06-20T23:21:43+02:00
ntdll: Use explicit ACTIVATION_CONTEXT type instead of HANDLE.
-
351a65e7
by Zhiyi Zhang at 2025-06-20T23:21:43+02:00
kernel32/tests: Add tests for normal activation context stack frame flags.
Test that the flags for normal activation context stack frames has 0x8, which is probably to note
that a frame is allocated from the heap according to later tests.
-
7b29dc90
by Zhiyi Zhang at 2025-06-20T23:21:43+02:00
ntdll: Set and check 0x8 flag for activation context stack frames.
Prepare for RtlActivateActivationContextUnsafeFast(), which adds frames with flags 0x20. Normal
frame flags are 0x28. So 0x8 is most likely to note that it's callee-allocated and needs to be freed
in RtlFreeActivationContextStack(). Whereas missing 0x8 probably means a frame is caller-allocated.
-
20db80f2
by Zhiyi Zhang at 2025-06-20T23:21:43+02:00
ntdll: Implement RtlActivateActivationContextUnsafeFast().
-
4f51853e
by Zhiyi Zhang at 2025-06-20T23:21:43+02:00
ntdll: Implement RtlDeactivateActivationContextUnsafeFast().
-
422d6763
by Zhiyi Zhang at 2025-06-20T23:21:43+02:00
kernel32/tests: Add tests for RtlActivateActivationContextUnsafe() and RtlDeactivateActivationContextUnsafeFast().