[NativeAOT] Add sampling profiler

[filipnavara]

Presumably this is pretty useless since we don't do the rundown to get readable method names... but since I already have it laying around, anyone can think of a use for this?

[dotnet-policy-service]

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

[MichalStrehovsky]

@LakshanF do you think we'd be able to implement the rest?

If there is a rundown for this, we do have names of methods available in stack trace metadata. If the rundown can run managed code, we could get it there. Maybe. Depending on what actually involves the rundown.

[filipnavara]

I only tried to run it with dotnet-trace and conversion to Speedscope format, which was quite useless, since you could see the stack traces but instead of method names there was just "?!?". I wonder if PerfView could perhaps show the addresses or correlate that to image base addresses. That would be already good enough for tools that can perform native symbolication (eg. Sentry).

Stack trace metadata sound like an interesting thing to try...

[LakshanF]

There is a work item in the diagnostic repo to lookup type information for native AOT GCDump, which could be expanded to include method information as well.

[dotnet-policy-service]

Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it.