[release/9.0] dont try to capture threadId for NativeAOT by github-actions[bot] · Pull Request #108088 · dotnet/runtime (original) (raw)

Backport of #108045 to release/9.0

/cc @mangod9

Customer Impact

• Customer reported
• Found internally

Regression

• Yes
• No

The new instrumentation change can potentially AV if the threadId isn't at 0x130 offset. Have put the specific code under config and excluded for NativeAOT

Testing

There hasn't been a reliable repro for the failures. Only seen in CI in the SDK repo currently. Based on the change sets this was found to be the likely culprit, and this change reduces the impact of the earlier instrumentation change

Risk

Low, adds a config so the new codepath is only exercised when the new config is specified.