-
Notifications
You must be signed in to change notification settings - Fork 510
Cannot debug graph visualisation #8043
Comments
Can you try leaving out this: |
I don't think the dependency graph will help you though. Try adding If you're not even getting that far (e.g. RyuJIT is crashing while compiling the method), your only option is to look at the generated IL in the debugger. We have a debugger visualizer for the |
Removing I will try |
Yup, that line would be useful to add. I used to write a piece of equivalent C#, compile with optimizations on, and disassemble that. But yes, at this point I know most of the important patterns by heart. |
Sign. I hope that you know some C# godbolt which can allow me write snippet and see the view of IL. Upon search I found https://sharplab.io/ Is it helpful to use? Because IL optimization likely can be trivial. Or I am miss something important? I'm more or less know IL. Have rusty knowledge and lack of practice. Also for Windows Forms DGML output and DependencyGraphViewer almost impractical to use 200Mb for trivial app. |
Yeah, sharplab.io should work. I use Yeah, the DGML is proportional to the size of the app. Windows.Forms drags in a lot of stuff. |
I attempt to make a stab at the marshalling null values for COM, but stuck with producing correct IL. I decide that I'm smart guy and can enable debugging of the DependencyGraph. I'm not sure if this was correct decision, but that's not root cause of the issue which I encounter.
So I start follow Documentation\how-to-debug-compiler-dependency-analysis.md
<IlcGenerateDgmlFile>true</IlcGenerateDgmlFile>
ILCompiler-DependencyGraph-Viewer.sln
dotnet publish
as adminILCompiler-DependencyGraph-Viewer
inside VSevents was not there.
Under debugger, line below return false into
restarted
variable.corert/src/ILCompiler.DependencyAnalysisFramework/ILCompiler-DependencyGraph-Viewer/Program.cs
Line 258 in 7f4555b
I suspect that this is related to enabling ETW somehow, or maybe I miss some other step?
The text was updated successfully, but these errors were encountered: