MacOS arm64 NAOT runtime-async - bad ResumeInfo written (causing failure on StackTraceTests)

[rcj1]

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1279690&view=results

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @dotnet/ilc-contrib
See info in area-owners.md if you want to be subscribed.

[jakobbotsch]

Is the

Fatal error. Invalid Program: attempted to call a UnmanagedCallersOnly method from managed code.

in the log unrelated?

[rcj1]

No; what happens is when we return from Foo2 into Foo1, and attempt to run the resumption of Foo1 (which should be the catch handler because Foo2 throws an exception in its finally), the ResumeInfo contains bad addresses (not sure exactly what is in there, but it looks like some flags on the high bits). We set a watchpoint on the second Continuation created for Foo1, and see that the bad data is written shortly before a call to CaptureContinuationContext, and after some adrp arithmetic. The calling of a bad address in DispatchContinuations then surfaces as the UnmanagedCallersOnly error.