Bring throw helpers to PUSH_COOP_PINVOKE_FRAME plan

[am11]

Fixes #116375.

[dotnet-policy-service]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

[jkotas]

If CreateThrowable throws OutOfMemoryException here, is it going to be handled gracefully?

[am11]

I think the original DispatchManagedException(kNullReferenceException) overload does the same thing internally; it calls CreateThrowable() which can throw OOM. So the behavior is unchanged. The exception frame (SoftwareExceptionFrame) is already set up and we're inside FC_CAN_TRIGGER_GC(), so if OOM is thrown, it will be dispatched normally through the existing exception handling machinery.

[jkotas]

As a test, I have added new int[(size_t)1000000000 * (size_t)1000000000]; here and run the following test (on Windows):

using System;

try {
    throw null;
}
catch (OutOfMemoryException) {
}

Expected behavior: The exception should be handled by the catch,
Actual behavior: The test failed with Unhandled exception. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.)

I think we are missing one of those macros that flips between C++ and managed exceptions here. @janvorli What's the right macro to use here?

(It is possible that this is broken in main currently - I have not tested that.)

[am11]

Thanks. I was primarily testing in CI and observed failures on both linux-arm64 and x64. With arm64 now fixed by updating the offset, I’ll look into what adjustments are needed for x64. In the meantime, I’ve reverted this change.