Giters

benaadams / Ben.Demystifier

High performance understanding for stack traces (Make error logs more productive)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

DisplayClass and MoveNext are showing up in the stack trace

jnm2 opened this issue · comments

commented

I didn't expect to see these words. Is this something that could be demystified?

Using Ben.Demystifier 0.1.6 and System.CommandLin 2.0.0-beta1.20427.1 on .NET Framework 4.8:

   at async Task<int> System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(object value, InvocationContext context)
   at async Task<int> System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
   at void System.CommandLine.Invocation.InvocationPipeline+<>c__DisplayClass4_0+<<BuildInvocationChain>b__0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c+<<UseParseErrorReporting>b__21_0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c__DisplayClass16_0+<<UseHelp>b__0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c__DisplayClass25_0+<<UseVersionOption>b__0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c__DisplayClass23_0+<<UseTypoCorrections>b__0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c+<<UseSuggestDirective>b__22_0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c+<<UseParseDirective>b__20_0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c+<<UseDebugDirective>b__11_0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c+<<RegisterWithDotnetSuggest>b__10_0>d.MoveNext()
   at void System.CommandLine.Builder.CommandLineBuilderExtensions+<>c__DisplayClass14_0+<<UseExceptionHandler>b__0>d.MoveNext()