Corrupting exceptions are not turned into fail fasts

[jkotas]

Repro:

It should not be possible to catch corrupting exceptions like AccessViolationExceptions.

using System;

class Test
{
    static unsafe void Main()
    {
        try {
            *(int*)0x1235678 = 0x12345;
        }
        catch (Exception e) {
            Console.WriteLine("Here");
        }
    }
}

Actual behavior

Here

Expected behavior

Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at Test.Main()

Known Issue Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[jkotas]

cc @janvorli @VSadov

[jkotas]

This blocks post-mortem debugging of CI crashes caused by access violations (e.g. see #102919).

[janvorli]

I've found the culprit, missing handling of access violation as a failfast in the GetClasslibException. I'll fix it.