如何防止 Visual Studio 2015 Update 2 添加 telemetry_main_invoke_trigger? [英] How to prevent Visual Studio 2015 Update 2 to add telemetry_main_invoke_trigger?

问题描述

我怎样才能防止这种情况发生?

解决方案

根据

Steve Carroll 解释说，这将在即将到来的更新 3 中删除:

<块引用>

我们的意图是良性的——我们的愿望是构建一个框架帮助调查性能问题并提高我们的质量优化器我们应该得到任何关于减速或地方性性能的报告领域的问题.我们为提高怀疑级别而道歉更进一步，不包括 CRT 源，这只是一个我们的监督.尽管如此，你们中的一些人已经调查过了这个机制是如何工作的，细节很好.正如你已经打电话出来，代码所做的是触发一个 ETW 事件，当它打开，将发出时间戳和模块加载事件.事件只有在客户向我们提供符号信息时才能解释数据(即 PDB)，因此此数据仅适用于以下客户积极寻求我们的帮助，并愿意将这些 PDB 作为他们调查的一部分.我们实际上还没有经历过这个迄今为止，与任何客户进行了充分的练习，到目前为止，我们依靠我们既定的方法来调查和解决而是潜在的问题.我们计划在更新中删除这些事件3. 同时，要在更新 2 中删除此依赖项，您应该将 noteelemetry.obj 添加到您的链接器命令行.

A simple C++ console app

int main()
{
  return 0;
}

compiled in Visual Studio 2015 Update 2 adds a call to telemetry_main_invoke_trigger to both Debug and Release binaries.

How can I prevent this?

解决方案

According to Microsoft’s Steve Carroll (Development Manager for the Visual C++ team), you can remove telemetry calls by adding notelemetry.obj to the command options of the linker:

Steve Carroll explained that this will be removed in the upcoming Update 3:

Our intent was benign – our desire was to build a framework that will help investigate performance problems and improve the quality of our optimizer should we get any reports of slowdowns or endemic perf problems in the field. We apologize for raising the suspicion levels even further by not including the CRT source, this was just an oversight on our part. Despite that, some of you already investigated how this mechanism works in nice detail. As you have already called out, what the code does is trigger an ETW event which, when it’s turned on, will emit timestamps and module loads events. The event data can only be interpreted if a customer gives us symbol information (i.e. PDBs) so this data is only applicable to customers that are actively seeking help from us and are willing to share these PDBs as part of their investigation. We haven’t actually gone through this full exercise with any customers to date though, and we are so far relying on our established approaches to investigate and address potential problems instead. We plan to remove these events in Update 3. In the meantime, to remove this dependency in Update 2, you should add notelemetry.obj to your linker command line.

这篇关于如何防止 Visual Studio 2015 Update 2 添加 telemetry_main_invoke_trigger?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！