[NativeAOT] No variables or object inspection when debugging class library

[Paril]

It seems that if you have a native executable that loads a NativeAOT-built class library, when stepping into the C# code, there's no ability to view variables or inspect the C# side of things at all (not even parameters, etc); is this intentional, or is something set up incorrectly on my end? I did see some people say that they could view variables/inspect objects in other issues, but I'm not sure why that's not possible in this case.

[ghost]

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

Issue Details

---

It seems that if you have a native executable that loads a NativeAOT-built class library, when stepping into the C# code, there's no ability to view variables or introspect the C# side of things at all (not even parameters, etc); is this intentional, or is something set up incorrectly on my end? I did see some people say that they could view variables/introspect objects in other issues, but I'm not sure why that's not possible in this case.

Author:	Paril
Assignees:	-
Labels:	area-NativeAOT-coreclr
Milestone:	-

[jkotas]

Could you please share more details about your environment:

• .NET runtime version
• Operating system
• Debugger

[vitek-karas]

Did the debugger find symbols for the NativeAOT-built library. The library behaves like native code, without symbols the debugger won't see pretty much anything.

/cc @LakshanF

[Paril]

This ended up being user error; I was using dotnet publish with -c Release, and apparently there's still the ability to step through stuff but no variable inspection. Everything looks much better with -c Debug, although some stuff can't be inspected (like ReadOnlySpans) but I assume that's just WIP.

[agocke]

This might be that DWARF information isn't as good as it could be. See #72552

I'll start looking into Release codegen specifically. We might be able to do better than we are right now.