baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester fails on Linux

[sandreenko]

It was disabled so we have not seen it, the log is:

  baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.sh [FAIL]
      
      Return code:      1
      Raw output file:      /root/helix/work/workitem/baseservices/exceptions/Reports/baseservices.exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.output.txt
      Raw output:
      BEGIN EXECUTION
      /root/helix/work/correlation/corerun stackoverflowtester.dll ''
      Running stackoverflow test(smallframe main)
      "Stack overflow."
      "Repeat 174461 times:"
      "--------------------------------"
      "   at TestStackOverflow.Program.InfiniteRecursionC()"
      "   at TestStackOverflow.Program.InfiniteRecursionB()"
      "   at TestStackOverflow.Program.InfiniteRecursionA()"
      "--------------------------------"
      "   at TestStackOverflow.Program.Test(Boolean)"
      "   at TestStackOverflow.Program.Main(System.String[])"
      "apply_reg_state: ip and cfa unchanged; stopping here (ip=0x7fb3fc0f2c)"
      Gathering state for process 522 corerun
      Writing minidump with heap to file /home/helixbot/dotnetbuild/dumps/coredump.522.dmp
      Written 61616128 bytes (15043 pages) to core file
      Dump successfully written
      ""
      Missing "Main" method frame at the last line
      Expected: 100
      Actual: 101
      END EXECUTION - FAILED

note that on some archs it fails with a timeout.

AzDo example.

[sandreenko]

PTAL @echesakovMSFT I believe you were working with this test.

[echesakov]

PTAL @echesakovMSFT I believe you were working with this test.

No, @janvorli created this test

[janvorli]

I had no idea the test was disabled. @sandreenko where have you seen it failing with timeout?

[sandreenko]

@janvorli it was in the same job, here the log https://dev.azure.com/dnceng/public/_build/results?buildId=923829&view=ms.vss-test-web.build-test-results-tab&runId=29324470&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=102790

Note: the test is disabled again, I have disabled it in #46162

[janvorli]

After I've fixed the lookup for the Main in the stack trace, the ARM64 legs are failing due to the fact that we don't have the probing helper change in yet. So for large frames, the failure point is too far from the SP, the failure is not recognized as stack overflow and the sigsegv alternate stack is not large enough to execute the full stack overflow reporting. The alternate stack is about two pages large while the stack overflow needs about 8 pages. We need to wait for the stack probing helper change to reenable the tests.
The OSX / Linux x64 legs are failing due to timeouts caused most likely by the fact that our test infra generates core dumps for the processes that the test launches and that are expectedly failing with the stack overflow. I'll look into a way to prevent dumps generation for the secondary processes.