Validate Native AOT experience in native debuggers

[agocke]

Since Native AOT uses a native debugging experience, compared to a managed one, a certain number of differences are expected. In particular, it's not expected that debugging AOT will have a managed view of the process and instead things will appear closer to C++ conventions.

However, we should validate that this view is roughly accurate and define expected mappings, e.g. properties -> get_/set_ methods.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Since Native AOT uses a native debugging experience, compared to a managed one, a certain number of differences are expected. In particular, it's not expected that debugging AOT will have a managed view of the process and instead things will appear closer to C++ conventions.

However, we should validate that this view is roughly accurate and define expected mappings, e.g. properties -> get_/set_ methods.

Author:	agocke
Assignees:	-
Labels:	Epic, untriaged, area-NativeAOT-coreclr
Milestone:	8.0.0

[agocke]

We've done some basic debugging here, looks OK. We'll wait for more customer feedback on things to fix.