Fix nongcheap test

[EgorBo]

Fixes #88507

It seems that it was assumed that ULONG is 64-bit type (which is not), replaced with stdint

[ghost]

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

Issue Details

---

To fix #88507

Author:	EgorBo
Assignees:	-
Labels:	area-Diagnostics-coreclr
Milestone:	-

[EgorBo]

/azp list

[azure-pipelines]

CI/CD Pipelines for this repository:

• runtime-coreclr outerloop
• runtime-coreclr jitstress
• runtime-coreclr jitstressregs
• runtime-coreclr jitstress2-jitstressregs
• runtime-coreclr gcstress0x3-gcstress0xc
• runtime-coreclr gcstress-extra
• runtime-coreclr r2r-extra
• runtime-coreclr jitstress-isas-x86
• runtime-coreclr jitstress-isas-arm
• runtime-coreclr jitstressregs-x86
• runtime-coreclr libraries-jitstressregs
• runtime-coreclr libraries-jitstress2-jitstressregs
• runtime-coreclr r2r
• runtime-coreclr runincontext
• runtime-coreclr crossgen2
• runtime-libraries-coreclr outerloop
• runtime-libraries-coreclr outerloop-windows
• runtime-libraries-coreclr outerloop-linux
• runtime-libraries-coreclr outerloop-osx
• runtime
• runtime-libraries enterprise-linux
• runtime-libraries stress-http
• runtime-libraries stress-ssl
• runtime-dev-innerloop
• runtime-coreclr crossgen2 outerloop
• coreclr-release-outerloop-nightly
• runtime-coreclr crossgen2-composite
• runtime-jit-experimental
• runtime-coreclr libraries-jitstress
• dotnet-linker-tests
• runtime-coreclr ilasm
• runtime-coreclr crossgen2-composite gcstress
• runtime-staging
• runtime-coreclr pgo
• runtime-coreclr libraries-pgo
• Antigen
• runtime-community
• Fuzzlyn
• runtime-coreclr superpmi-replay
• runtime-wasm
• runtime-coreclr superpmi-diffs
• runtime-coreclr superpmi-asmdiffs-checked-release
• runtime-extra-platforms
• jit-cfg
• runtime-wasm-perf
• runtime-llvm
• runtime-coreclr jitstress-random
• runtime-coreclr libraries-jitstress-random
• runtime-android-grpc-client-tests
• runtime-wasm-libtests
• runtime-wasm-non-libtests
• runtime-android
• runtime-androidemulator
• runtime-ioslike
• runtime-ioslikesimulator
• runtime-linuxbionic
• runtime-maccatalyst
• runtime-coreclr pgostress
• runtime-coreclr jitstress-isas-avx512
• runtime-tools-tests
• runtime-libraries-mono outerloop
• runtime-sanitized
• runtime-wasm-dbgtests
• runtime-wasm-optional

[EgorBo]

/azp run runtime-coreclr jitstress2-jitstressregs, runtime-coreclr jitstressregs

[azure-pipelines]

No commit pushedDate could be found for PR 89711 in repo dotnet/runtime

[EgorBo]

/azp run runtime-coreclr jitstress2-jitstressregs, runtime-coreclr jitstressregs

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[EgorBo]

/azp run runtime-coreclr jitstress2-jitstressregs, runtime-coreclr jitstressregs

[azure-pipelines]

No commit pushedDate could be found for PR 89711 in repo dotnet/runtime

[EgorBo]

/azp run runtime-coreclr jitstress2-jitstressregs, runtime-coreclr jitstressregs

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[EgorBo]

@cshung PTAL, this fixes #88507

the crash was basically:

GetNonGCHeapBounds (segCount = 1): seg#0, rangeStart=0xffc858bb1008, rangeLength=6640, rangeLengthReserved=4194296 GetGenerationBounds (segCount = 5): seg#0, rangeStart=0xff8854000028, rangeLength=16368, rangeLengthReserved=33554392 seg#1, rangeStart=0xff8856c00028, rangeLength=0, rangeLengthReserved=33554392 seg#2, rangeStart=0xff8858c00028, rangeLength=0, rangeLengthReserved=4194264 seg#3, rangeStart=0xff8856800028, rangeLength=40544, rangeLengthReserved=4194264 seg#4, rangeStart=0xff8856000028, rangeLength=0, rangeLengthReserved=4194264 Fail: Overlapping segments 

it detected overlapping segments despite the fact they're not in fact overlapped - it happened because of mixing UINT_PTR (64-bit) and ULONG (32-bit even on 64-bit).

[EgorBo]

/azp run runtime-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[cshung]

Thanks