[WIP] Automatically get exception message and set to Span.Status

[reyang]

This is a follow up to the previous PR comment.
To play with the current code, use docs\trace\exception-handling> dotnet run --framework net5.0.

Current thinking:

1. Examine the EXCEPTION_RECORD.ExceptionCode, if code is 0xE0434352, proceed to step 2, otherwise exit since it is not a CLR Exception.
2. Examine if side-by-side CLR is enabled, and if yes, check if the exception belongs to the current CLR module?
3. Extract the EXCEPTION_RECORD, fetch the System.Exception object (might need to pin the object on GC?).
4. Access the exception object's detail via field or method call.
5. Unpin the exception object? (if pinned on step 2)

Reference:

• NT Exception: EXCEPTION_POINTERS and EXCEPTION_RECORD
• A Crash Course on the Depths of Win32™ Structured Exception Handling
• COMPLUS ExceptionCode: https://github.com/dotnet/runtime/blob/79ae74f5ca5c8a6fe3a48935e85bd7374959c570/src/coreclr/inc/corexcep.h#L20
• CLR Exception: https://github.com/dotnet/runtime/blob/79ae74f5ca5c8a6fe3a48935e85bd7374959c570/src/coreclr/inc/ex.h#L134
• My old code playing around exception handling and debugger API.

[codecov]

Codecov Report

Merging #1874 (07fd41a) into main (cb066cb) will decrease coverage by 0.40%.
The diff coverage is 79.27%.

@@            Coverage Diff             @@
##             main    #1874      +/-   ##
==========================================
- Coverage   83.77%   83.36%   -0.41%     
==========================================
  Files         187      188       +1     
  Lines        5967     6139     +172     
==========================================
+ Hits         4999     5118     +119     
- Misses        968     1021      +53     

Impacted Files	Coverage Δ
src/OpenTelemetry/Sdk.cs	100.00% <ø> (ø)
src/OpenTelemetry/Logs/OpenTelemetryLogger.cs	26.82% <20.54%> (-44.60%)	⬇️
src/OpenTelemetry/Logs/LogRecord.cs	82.50% <77.77%> (-5.00%)	⬇️
.../OpenTelemetry/Logs/OpenTelemetryLoggerProvider.cs	77.55% <88.23%> (+7.09%)	⬆️
...rc/OpenTelemetry/Trace/TracerProviderBuilderSdk.cs	89.83% <91.66%> (-0.92%)	⬇️
src/OpenTelemetry/Trace/ExceptionProcessor.cs	93.75% <93.75%> (ø)
src/OpenTelemetry/Trace/TracerProviderSdk.cs	95.16% <98.64%> (+4.38%)	⬆️
...metryProtocol/Implementation/ActivityExtensions.cs	86.89% <100.00%> (+0.05%)	⬆️
...ry.Instrumentation.AspNet/AspNetInstrumentation.cs	100.00% <100.00%> (ø)
...umentation.AspNet/Implementation/HttpInListener.cs	89.10% <100.00%> (ø)
... and 22 more

[reyang]

Need to dig into https://github.com/dotnet/runtime/blob/79ae74f5ca5c8a6fe3a48935e85bd7374959c570/src/coreclr/vm/clrex.cpp#L653.

[reyang]

And https://github.com/dotnet/runtime/blob/79ae74f5ca5c8a6fe3a48935e85bd7374959c570/src/coreclr/inc/ex.h#L32.

[reyang]

The actual layout of the ExceptionInformation array is depending on the implementation:

• https://github.com/dotnet/runtime/blob/79ae74f5ca5c8a6fe3a48935e85bd7374959c570/src/coreclr/inc/ex.h#L38
• https://github.com/dotnet/runtime/blob/79ae74f5ca5c8a6fe3a48935e85bd7374959c570/src/coreclr/inc/ex.h#L49
• https://github.com/dotnet/runtime/blob/79ae74f5ca5c8a6fe3a48935e85bd7374959c570/src/coreclr/vm/clrex.cpp#L2156

[reyang]

ExceptionInformation[4] has different meaning depending on the condition compilation - related to side-by-side.

[reyang]

!sos.pe might give some clue, worst case is that the logic is duplicated in mscordacwks.dll...

[reyang]

This points to the base image address of clr.dll or coreclr.dll.