一些TPLETWProvider方法的参数太多-导致过多的调试输出 [英] Some TPLETWProvider methods have too many parameters - causes excessive debug output

问题描述

我在stackoverflow帖子中概述了该问题:

http://stackoverflow.com/questions/42123222/tpl-etw-events-have-extra-parameters-that-c​​ause-excessive-debugger-output

似乎有两个TPLETWProvider事件编写了有关参数数量不匹配的调试消息.  例如，

事件7用5个参数调用，但它是用6个参量定义的.

所讨论的两个方法在EventSource方法上具有额外的未使用参数，即"int appDomain".  

PS参数"拼写错误:在资源文件中.

这真的很烦人，因为它充满了诊断工具"窗口.通常会在安装了Stackify Prefix之类的探查器之后发生.

I have outlined the problem on a stackoverflow post:

http://stackoverflow.com/questions/42123222/tpl-etw-events-have-extra-parameters-that-cause-excessive-debugger-output

It seems the a couple of the TPLETWProvider events write debug message about number of parameters being mismatched.  For example,

Event 7 was called with 5 argument(s) , but it is defined with 6 paramenter(s).

The two methods in question have an extra unused parameter on the EventSource method, "int appDomain".  

PS "parameter(s)" is spelled wrong: "paramenter(s)" in the resource file.

It is really annoying as it floods my Diagnostic Tools window. This usually occurs after installing a profiler like Stackify Prefix.

推荐答案

我还应该包括这些截屏，显示调试器在这些功能上已停止

I should also include these screen shots showing the debugger stopped on these functions,

这篇关于一些TPLETWProvider方法的参数太多-导致过多的调试输出的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！