Enable Use-After-Return detection in AddressSanitizer

[jkoritzinsky]

Use-After-Return detection was disabled when AddressSanitizer was initially stood up because various components in CoreCLR (and possibly NativeAOT) check if a pointer is on the current thread's stack, which doesn't work with the fake stacks that the Use-After-Return detection uses to implement the feature. AddressSanitizer has APIs in its "public interface" that we can use to detect if a pointer is in the current thread's fake stack. We should use this feature in the places where we are asserting that a particular pointer points to the thread's stack and enable the detection.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Use-After-Return detection was disabled when AddressSanitizer was initially stood up because various components in CoreCLR (and possibly NativeAOT) check if a pointer is on the current thread's stack, which doesn't work with the fake stacks that the Use-After-Return detection uses to implement the feature. AddressSanitizer has APIs in its "public interface" that we can use to detect if a pointer is in the current thread's fake stack. We should use this feature in the places where we are asserting that a particular pointer points to the thread's stack and enable the detection.

Author:	jkoritzinsky
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[jkoritzinsky]

Green threads had a similar issue. This commit has the places that needed to be updated: dotnet/runtimelab@ba2a40d#diff-2683b20032662221023affe4d7e1a689fd966abfe1bd44fb6b65b83571a127ddR2994

Look for the stackPointerLessThan helper.