Test failure: JIT/Directed/throwbox/filter/filter.dll

[v-wenyuxu]

Failed in: runtime-coreclr jitstress-random 20250323.1

Failed tests:

coreclr osx arm64 Checked jitstress_random_2 @ osx.13.arm64.open
    - JIT/Directed/throwbox/filter/filter.dll

Error message:

 An object that does not derive from System.Exception has been wrapped in a RuntimeWrappedException.

Stack trace:

   at Program.<<Main>$>g__TestExecutor28|0_29(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)

[jkotas]

Regression from inlining methods with EH?

C++ (and maybe VB?) has exceptions that do not inherit from System.Exception. The runtime will wrap these non-standard exceptions in RuntimeWrappedException in assemblies written in languages like C# that expect exceptions to inherit from System.Exception.

This wrapping/unwrapping of exceptions is controlled by per-assembly setting (RuntimeCompatibilityAttribute.WrapNonExceptionThrows). When the EH is inlined cross assemblies, the runtime will read this setting from wrong assembly.

We may need to disable inlining EH between assemblies with different WrapNonExceptionThrows settings. Look for Module::IsRuntimeWrapExceptions in the VM.

cc @AndyAyersMS

[AndyAyersMS]

Is there something similar for NAOT?

[AndyAyersMS]

Also a bit odd that this doesn't repro on other platforms. The test is run with TC=0, jitstress behavior shouldn't generally be platform specific; the coreclr test runner doesn't randomize test order...

[jkotas]

NAOT does not support these: First point in #69919

[AndyAyersMS]

We inline the test entry point into the wrapper. The test is IL

Inlines into 06000020 [via RandomPolicy] Program:<<Main>$>g__TestExecutor28|0_29(System.IO.StreamWriter,System.IO.StreamWriter,byref):
...
  [INL08 IL=-101058055 TR=000030 06000001] [INLINED: call site: random accept] JitTest.Test:Main():int
    [INL00 IL=0005 TR=000257 0600008C] [FAILED: callee: noinline per IL/cached result] System.Console:WriteLine(System.String)
    [INL00 IL=0028 TR=000270 0600008C] [FAILED: call site: within filter region] System.Console:WriteLine(System.String)
    [INL00 IL=0066 TR=000305 0600008C] [FAILED: call site: within filter region] System.Console:WriteLine(System.String)
    [INL00 IL=0079 TR=000298 0600008C] [FAILED: call site: within filter region] System.Console:WriteLine(System.String)
    [INL00 IL=0092 TR=000310 0600008C] [FAILED: call site: within catch region] System.Console:WriteLine(System.String)

Seems like in general we probably don't expect these test methods to be inlined.