Visual Studio 2022诊断工具总是显示“尚未收集数据”。

发布于 2025-01-27 02:11:33 字数 167 浏览 2 评论 0原文

Visual Studio 2022社区中的诊断工具已停止工作。它显示它正在录制CPU配置文件,但是每当我暂停程序以查看结果时,工具说“没有收集数据”。

它在某一时刻工作,据我所知,我没有更改任何内容,如果我进入过滤器下拉菜单,则显示了所有内容,除了选择“隐藏本机代码”之外。

我该如何解决?

The diagnostic tools in Visual Studio 2022 Community have stopped working. It shows it's recording the CPU profile but whenever I pause the program to see the results, the tools say "There is no data collected."

It was working at one point, and as far as I'm aware, I didn't change anything and if I go into the filter drop-down menu it shows everything except "Hide native code" is selected.

How can I fix this?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

猫弦 2025-02-03 02:11:33

就我而言,这是由于服务的“ Visual Studio Collector Service 150”被停止或禁用,因此不运行。一旦启用服务并重新运行“调试”,诊断工具似乎再次起作用。

In my case it happened due to service 'Visual Studio Collector Service 150" being stopped, or disabled, and therefore, not running. Once you enable the service, and re-run 'debug', diagnostic tools seem to be working, again.

入画浅相思 2025-02-03 02:11:33

我今天遇到了这个问题。将Visual Studio 2022更新为最新版本后,诊断工具已恢复,现在正常运行。更新过程似乎基本上重新安装了VS,我认为它是从其意外状态重置VS的。

I encountered this issue today. The Diagnostic Tools have been restored and are now functioning properly after updating Visual Studio 2022 to the latest version. The update process appeared to essentially reinstall VS, which I believe reset the VS from its unexpected state.

月下伊人醉 2025-02-03 02:11:33

几个原因而发生的

  • 这可能是由于您的代码未执行的 。这是最有可能的解释。如果程序正常启动,则无法运行代码。在特定代码部分的开头中放一个断点,看看Visual Studio是否停止了那里。尝试使用main(..)函数输入点要开始。
  • 您没有在构建中包含程序配置文件信息。您是否正在构建调试版本,是否关闭了调试信息或分析信息?您是否在解决方案或项目属性页面上打开它们?
  • 您正在使用编译器或链接选项构建,以防止分析信息包含在您的可执行文件中。

This could happen for a few reasons

  • Your code did not execute. This is the most likely explanation. The program, if it started properly, didn't get as far as running your code. Put a break-point at the start of your particular code section and see if Visual Studio stops there. Try putting on the main(..) function entry point to start.
  • You didn't include program profile information in the build. Are you building a Debug version, have you turned off debug information or profiling information? Have you turned them on in the solution or project property pages?
  • You are building with compiler or linking options that prevent profiling information from being included in your executable.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文