Diagnostics: Compatibility with preview 6

[jmezach]

I've just upgraded to the preview 6 bits of .NET Core and noticed that the preview 5 versions of dotnet counters and dotnet dump aren't compatible with it (not sure about dotnet trace). When running dotnet counters monitor I'm basically getting nothing at all. Using dotnet dump collect works, but subsequently analysing the resulting dump using dotnet dump analyze fails with the following exception:

Unhandled exception: System.TypeInitializationException: The type initializer for 'SOS.LLDBServicesWrapper' threw an exception. ---> System.MissingMethodException: Method not found: 'Boolean SOS.SymbolReader.InitializeSymbolStore(Boolean, Boolean, Boolean, System.String, System.String, System.String)'.
   --- End of inner exception stack trace ---
   at SOS.LLDBServicesWrapper..ctor(SOSHost host, IDataReader dataReader, ISOSHostContext context) in /_/src/SOS/SOS.Hosting/LLDBServicesWrapper.cs:line 128
   at SOS.SOSHost..ctor(IDataReader dataReader, ISOSHostContext context) in /_/src/SOS/SOS.Hosting/SOSHost.cs:line 57
   at Microsoft.Diagnostic.Tools.Dump.AnalyzeContext.get_SOSHost() in /_/src/Tools/dotnet-dump/AnalyzeContext.cs:line 60
   at Microsoft.Diagnostic.Tools.Dump.Analyzer.Analyze(FileInfo dump_path, String[] command) in /_/src/Tools/dotnet-dump/Analyzer.cs:line 53
   at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
   at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass3_0.<<InvokeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseErrorReporting>b__16_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c__DisplayClass8_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseSuggestDirective>b__7_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseDebugDirective>b__4_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseDirective>b__6_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseHelp>b__14_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass3_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<RegisterWithDotnetSuggest>b__17_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseExceptionHandler>b__5_0>d.MoveNext()

Are there any plans to ship preview 6 versions of these tools?

[sywhang]

Sorry you ran into that -- we had some infrastructure issues in this repo that prevented us from pushing out Preview 6 versions of the CLI tools on the same date as the rest of the SDK went out.

I remember the release date for the diagnostics tools being either tomorrow or the day after that, but @mikem8361 would know the exact answer to that.

cc @tommcdon

[jmezach]

Ah, I see. No worries. Thanks for the quick reply. Now I'm hoping these bits will come out in time for my demo next week ;).

[sywhang]

You can choose to build this repo yourself and install the package that gets built. I'm pretty sure I can look up how to do that for you (I've done it before) in the unlikely case we don't get to ship by EOW :-)

[mikem8361]

If you want to install the what will be the Preview 6 tools you can use this command:

$ dotnet tool install -g dotnet-dump --version  1.0.4-preview6.19311.1 --add-source https://dotnetfeed.blob.core.windows.net/dotnet-core/index.json

And you can replace dotnet-dump with any of our other tools.

[jmezach]

Ah, yes, that works. Unfortunately my demo issue regarding gcroot isn't fixed with this release ;). It just sits there and does nothing.

[mikem8361]

Just give it some more time. Some commands like gcroot take a lot longer under dotnet-dump, but they eventually finish.