GC Stress failure: Assert failure(PID 3732 [0x00000e94], Thread: 2904 [0x0b58]): curOffset <= infoPtr->methodSize

[AndyAyersMS]

Windows, x86

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1191254&view=ms.vss-test-web.build-test-results-tab

set DOTNET_TieredCompilation=0
set DOTNET_GCStress=0x3

14:51:43.076 Running test: JIT/CodeGenBringUpTests/ArrayExc_do/ArrayExc_do.dll

Assert failure(PID 3732 [0x00000e94], Thread: 2904 [0x0b58]): curOffset <= infoPtr->methodSize

CORECLR! DecodeGCHdrInfo + 0x10D (0x73c8bbbd)
CORECLR! EECodeInfo::DecodeGCHdrInfoHelper + 0x3F (0x73ce2b57)
CORECLR! StackFrameIterator::ProcessIp + 0xAE (0x73da3e07)
CORECLR! StackFrameIterator::Init + 0x15E (0x73da2f61)
CORECLR! Thread::StackWalkFramesEx + 0xCB (0x73da43d4)
CORECLR! Thread::HandledJITCase + 0x1AB (0x73f82561)
CORECLR! Thread::Hijack + 0xEC (0x73f8276d)
CORECLR! ThreadSuspend::SuspendAllThreads + 0x13F (0x73f85a1a)
CORECLR! ThreadSuspend::SuspendEE + 0x18D (0x73f85c5b)
CORECLR! GCToEEInterface::SuspendEE + 0x48 (0x73e767c3)
    File: D:\a\_work\1\s\src\coreclr\vm\gc_unwind_x86.inl:150
    Image: C:\h\w\ADBE09BC\p\corerun.exe

[dotnet-policy-service]

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

[jkotas]

The IP is pointing at R2R thunk:

729daaa0 33c0            xor     eax,eax  <------------
729daaa2 6a01            push    1
729daaa4 ff3574603373    push    dword ptr [System_Private_CoreLib+0xff6074 (73336074)]
729daaaa ff2580603373    jmp     dword ptr [System_Private_CoreLib+0xff6080 (73336080)]
729daab0 0000            add     byte ptr [eax],al

We are trying to interpret this IP as managed code. We found bogus GC info for it and crashing while trying to decode this bogus GC info.

@jkoritzinsky This looks like a regression from the recent R2R refactoring PRs.

[jkoritzinsky]

Looks like there's a bug in the "range" symbol handling for the last element of the range. Should have fix out soon.

[AndyAyersMS]

There were quite a few failures in gcstress extra too, maybe related? You may want to run that on your fix.

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1191380&view=ms.vss-test-web.build-test-results-tab

[AndyAyersMS]

I started one: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1193210&view=results